Bug 1097770 - Destination specific CLI operations aren't available in domain mode
Summary: Destination specific CLI operations aren't available in domain mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.2.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ER9
: EAP 6.3.0
Assignee: Jeff Mesnil
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-14 13:45 UTC by Tyronne Wickramarathne
Modified: 2018-12-06 16:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 14:38:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-4705 0 Major Resolved differences between registered and described operations for messaging resources in domain mode 2015-11-02 11:01:30 UTC

Description Tyronne Wickramarathne 2014-05-14 13:45:30 UTC
Description of problem:
It is not possible to obtain message count or remove message from a destination (Queue) when HornetQ is used in domain mode. 

The remove-messages() operation is vital specially to purge messages from the configured DLQ.

Version-Release number of selected component (if applicable):
HornetQ-2.3.12.Final

How reproducible:
Always


Steps to Reproduce:
1. Configure a destination and a DLQ as follows in full or full-ha profile in domain mode:

                <jms-destinations>
                    <jms-queue name="A">
                        <entry name="java:/jboss/exported/queue/A"/>
                        <durable>true</durable>
                    </jms-queue>
                    <jms-queue name="DLQ">
                        <entry name="java:/jboss/exported/queue/DLQ"/>
                        <durable>true</durable>
                    </jms-queue>
                </jms-destinations>


2. Please configure redelivery-delay at "0" for immediate redelivery for this test and max-delivery-attempts to 1 for this test :

<address-setting match="#">
   <dead-letter-address>jms.queue.DLQ</dead-letter-address>
   <expiry-address>jms.queue.ExpiryQueue</expiry-address>
   <redelivery-delay>0</redelivery-delay> <!-- HERE -->
   <max-size-bytes>10485760</max-size-bytes>
   <address-full-policy>PAGE</address-full-policy>
   <page-size-bytes>2097152</page-size-bytes>
   <max-delivery-attempts>1</max-delivery-attempts> <!-- HERE -->
   <message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>

3. Send N number of messages to queue/A. 
4. Configure a consumer to throw an exception during message delivery to force the message(s) in DLQ  
5. Try to access the message count via CLI, the CLI does not expose methods to view message count or to purge them from the given Queue.

Actual results:
The domain mode does not offer methods to remove or view message count

Expected results:
The application server should allow users to view message count and purge messages in domain mode

Additional info:

Comment 3 Jeff Mesnil 2014-07-08 13:02:55 UTC
this issue was fixed in upstream AS7-4705

Comment 4 Miroslav Novak 2014-07-08 13:15:01 UTC
I tried with EAP 6.3.0.ER9. I'll change status of this bz to verified. Thanks Jeff!


Note You need to log in before you can comment on or make changes to this bug.