Bug 1132170 - [GSS] (6.3.1) TopicControl.listDurableSubscriptionsAsJSON does not work with hierarchical topics
Summary: [GSS] (6.3.1) TopicControl.listDurableSubscriptionsAsJSON does not work with ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.3.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: CR1
: EAP 6.3.1
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On: 1113908
Blocks: eap631-blockers, eap631-payload, eap63-cp01-blockers 1132169
TreeView+ depends on / blocked
 
Reported: 2014-08-20 20:34 UTC by Jimmy Wilson
Modified: 2018-12-09 18:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1113908
Environment:
Last Closed: 2014-10-13 18:39:31 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1372 0 Major Closed TopicControl.listDurableSubscriptionsAsJSON does not work with hierarchical topics 2017-06-08 06:35:46 UTC

Description Jimmy Wilson 2014-08-20 20:34:34 UTC
+++ This bug was initially created as a clone of Bug #1113908 +++

Description of problem:
JConsole throws an "IllegalArgumentException" when trying to obtain the list of subscribers for a Topic.

Version-Release number of selected component (if applicable):
JBoss-EAP-6.2, JBoss-EAP-6.3-Beta

How reproducible:
Always

Steps to Reproduce:
1. Please create two Topics as follows :
                <jms-destinations>
                    <jms-topic name="my.jms.#">
		       <entry name="jms/all"/>
                       <entry name="java:jboss/exported/jms/all"/>
		    </jms-topic>
                    <jms-topic name="my.jms.A">
                       <entry name="jms/A"/>
                       <entry name="java:jboss/exported/jms/A"/>
		    </jms-topic>
                </jms-destinations>
2. Start the server and open the JConsole 
3. Please access "my.jms.A" Topic (jboss.as:subsystem=messaging,hornetq-server=default,jms-topic=my.jms.A)
4. Please invoke listAllSubscriptionsAsJson operation


Actual results:
5. The JConsole would throw "java.lang.IllegalArgumentException: Invalid message queue name: my.jms.A" exception
6. In the server log, the following exception can be seen :
15:44:55,575 ERROR [stderr] (pool-1-thread-2) java.lang.IllegalArgumentException: Invalid message queue name: jms.topic.my.jms.#
15:44:55,576 ERROR [stderr] (pool-1-thread-2) 	at org.hornetq.jms.client.HornetQDestination.decomposeQueueNameForDurableSubscription(HornetQDestination.java:122)
15:44:55,576 ERROR [stderr] (pool-1-thread-2) 	at org.hornetq.jms.management.impl.JMSTopicControlImpl.listSubscribersInfosAsJSON(JMSTopicControlImpl.java:321)
15:44:55,577 ERROR [stderr] (pool-1-thread-2) 	at org.hornetq.jms.management.impl.JMSTopicControlImpl.listAllSubscriptionsAsJSON(JMSTopicControlImpl.java:164)
15:44:55,578 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.messaging.jms.JMSTopicControlHandler.executeRuntimeStep(JMSTopicControlHandler.java:101)
15:44:55,578 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
15:44:55,579 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
15:44:55,579 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
15:44:55,580 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
15:44:55,580 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
15:44:55,581 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194)
15:44:55,581 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115)
15:44:55,582 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.execute(ModelControllerMBeanHelper.java:406)
15:44:55,582 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:384)
15:44:55,583 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:358)
15:44:55,583 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:134)
15:44:55,584 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:263)
15:44:55,584 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:915)
15:44:55,585 ERROR [stderr] (pool-1-thread-2) 	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
15:44:55,585 ERROR [stderr] (pool-1-thread-2) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
15:44:55,585 ERROR [stderr] (pool-1-thread-2) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
15:44:55,586 ERROR [stderr] (pool-1-thread-2) 	at java.lang.Thread.run(Thread.java:744)



Expected results:
The method should list the available subscribers without throwing an exception.

--- Additional comment from  on 2014-07-17 17:42:09 EDT ---

This issue really wasn't related at all to JConsole so I've updated the title to be more precise.

--- Additional comment from  on 2014-07-21 11:28:56 EDT ---

This was fixed on the 2.4.x branch of HornetQ via commit bc4e24bc82760afca5c243a7bc3b9aa82712c4ed.

--- Additional comment from JBoss JIRA Server on 2014-07-21 11:36:56 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Resolved

--- Additional comment from JBoss JIRA Server on 2014-07-21 12:36:03 EDT ---

Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1372 to Reopened

--- Additional comment from JBoss JIRA Server on 2014-07-21 12:36:17 EDT ---

Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1372 to Closed

--- Additional comment from Clebert Suconic on 2014-08-05 10:13:13 EDT ---

It needs a 2.3.x commit (PR)

--- Additional comment from Clebert Suconic on 2014-08-05 14:01:20 EDT ---

https://github.com/hornetq/hornetq/pull/1758

--- Additional comment from  on 2014-08-05 14:13:16 EDT ---

This was fixed on the 2.3.x branch of HornetQ via commit 067dfbbb866c60e6a8ebed59ec6f005b08a6a76b.

--- Additional comment from JBoss JIRA Server on 2014-08-05 14:30:51 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Reopened

--- Additional comment from JBoss JIRA Server on 2014-08-05 14:31:52 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Resolved

--- Additional comment from JBoss JIRA Server on 2014-08-05 14:31:59 EDT ---

Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Closed

Comment 1 Miroslav Novak 2014-08-28 13:50:24 UTC
Verified in EAP 6.3.1.CP.CR1. Thanks for the fix!


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