Description of problem: ======================= Looks like the API [1] is using hardcoded hornetQ server name as "default" inside the "QueueMetrics.java" as following: {code} final HelpSystem.AddressCallback addressCallback = new HelpSystem.AddressCallback() { @Override public ModelNode getAddress() { ModelNode address = new ModelNode(); address.get(ModelDescriptionConstants.ADDRESS).set(RuntimeBaseAddress.get()); address.get(ModelDescriptionConstants.ADDRESS).add("subsystem", "messaging"); address.get(ModelDescriptionConstants.ADDRESS).add("hornetq-server", "default"); address.get(ModelDescriptionConstants.ADDRESS).add("jms-queue", "*"); return address; } }; {code} - Above is causing issue if someone alters the "Hornetq-server" name to something else. In that case the Console will not be able to display the QueueMetrics for any JMS Queue or Topic. - See attached Screenshot with the When the HornetQ server name was changed to "testing" {code} <subsystem xmlns="urn:jboss:domain:messaging:2.0"> <hornetq-server name="testing"> . . </hornetq-server> </subsystem> {code} [1] https://github.com/hal/core/blob/master/gui/src/main/java/org/jboss/as/console/client/shared/runtime/jms/QueueMetrics.java Version-Release number of selected component (if applicable): How reproducible: ================= Steps to Reproduce: 1. Create a JMS queue in a standalone-full profile as following: {code} /subsystem=messaging/hornetq-server=default/jms-queue=TestQueue1/:add(entries=["java:jboss/exported/TestQueue1"],durable=false) {code} 2. Now Edit the messaging subsystem manually and then edit the hornetq-server name to something else (other than "default") {code} <subsystem xmlns="urn:jboss:domain:messaging:1.3"> <hornetq-server name="testing"> . . </hornetq-server> </subsystem> {code} 3. Now restart the JBoss EAP6 and then access the following URL: (Won't find any Queue in the console) http://localhost:9990/console/App.html#jms-metrics Actual results: =============== JMS metrics is not visible/accessible for the defined queue. Expected results: =============== JMS metrics should have been displayed properly. Additional info:
Moving to 6.4 as the issue is still valid for 6.3 Example of affected use case is a HA configuration of HornetQ when there are 2 HQ servers configured for EAP instance (default and backup). If default dies user wont be able to access statistics from backup server via Admin Console.
Should this still remain in POST state?
Verifeid 6.4.0.DR12