Bug 1082606 - Console uses hardcoded hornetq-server name as "default" causes issue while monitoring JMS metrics
Summary: Console uses hardcoded hornetq-server name as "default" causes issue while mo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR1
: EAP 6.4.0
Assignee: Heiko Braun
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-31 13:09 UTC by Jay SenSharma
Modified: 2019-08-19 12:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3191 0 Major Resolved Console uses hardcoded hornetq-server name as "default" 2016-05-21 14:50:43 UTC

Description Jay SenSharma 2014-03-31 13:09:27 UTC
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:

Comment 1 Jakub Cechacek 2014-07-16 11:30:46 UTC
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.

Comment 2 Pavel Jelinek 2014-11-26 09:30:43 UTC
Should this still remain in POST state?

Comment 3 Jakub Cechacek 2014-12-09 15:51:06 UTC
Verifeid 6.4.0.DR12


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