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.
This issue really wasn't related at all to JConsole so I've updated the title to be more precise.
This was fixed on the 2.4.x branch of HornetQ via commit bc4e24bc82760afca5c243a7bc3b9aa82712c4ed.
Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Resolved
Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1372 to Reopened
Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1372 to Closed
It needs a 2.3.x commit (PR)
https://github.com/hornetq/hornetq/pull/1758
This was fixed on the 2.3.x branch of HornetQ via commit 067dfbbb866c60e6a8ebed59ec6f005b08a6a76b.
Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Reopened
Justin Bertram <jbertram> updated the status of jira HORNETQ-1372 to Closed
Appears to be fixed by HQ upgrade to 2.3.21 https://bugzilla.redhat.com/show_bug.cgi?id=1132168. Setting to MODIFIED.
In 6.4.0.DR1 there are still issues with JConsole. I tried to reproduce this bug as is described in reproducer and I'm getting error showed in attachment In 6.3.1 CP builds were not any issues and bug was fixed correctly.
Created attachment 938456 [details] new error
The error you're seeing now (i.e. "ClassNotFoundException: org.jboss.as.controller.OperationFailedRuntimeException (no security manager: RMI class loader disabled)) appears unrelated to the original problem. Do you see an error on the server when you invoke listAllSubscriptionsAsJson from JConsole?
I'm sorry I missed your comment, next time please use "needinfo" flag or change status to ON_QA. In server console isn't any error. Just in Jconsole. We tried another case, when jmx in hornetq is enabled and listAllSubscriptionsAsJson is invoked directly from hornetq mbean. In this case everything is working fine.
The error you're seeing now (i.e. "ClassNotFoundException: org.jboss.as.controller.OperationFailedRuntimeException (no security manager: RMI class loader disabled)) is unrelated to the original problem as far as I can see. Furthermore, I don't see how this could be a HornetQ problem since the referenced class is not shipped in HornetQ, there is no error logged on the server, and the operation works fine when used via the HornetQ MBean.
We can't verify this BZ right now because we are not able to perform reproducer without errors. We will open new BZ blocking this one on scripts and commands component.
this issue is blocked by https://github.com/wildfly/wildfly-core/pull/419
Kabir Khan <kabir.khan> updated the status of jira WFCORE-492 to Closed
https://github.com/wildfly/wildfly-core/pull/419 has been merged
Setting target milestone to ER1 as there could be fix for jconsole and we could verify this issue.
VERIFIED with 6.4.0.ER1