Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2069

Composite STOMP destination shows misleading JMX information

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • JBoss A-MQ 6.3
    • broker
    • Hide

      Using any STOMP client, subscribe to a composite destination, such as "/queue/test1,/queue/test2'. Find the corresponding JMX MBean, which will have a name that is a mangled version of the composite destination name. Note that some of the JMX attributes have incorrect values.

      Show
      Using any STOMP client, subscribe to a composite destination, such as "/queue/test1,/queue/test2'. Find the corresponding JMX MBean, which will have a name that is a mangled version of the composite destination name. Note that some of the JMX attributes have incorrect values.

      Consumer connections from STOMP clients that use composite destinations ("dest1,dest2") are represented in JMX differently from JMS clients. The representation seems to be appropriate for a single consumer ,rather than a composite. At least some of the values seems to be incorrect.

      For example, the "enqueue count" and "dequeue count" values never change, regardless of the number of messages passed. The "consumer count" value is always one below the actual number of consumers (so if no consumers are connected, it shows -1). I suspect that some of the other values are also wrong, but it's harder to test them definitively.

              Unassigned Unassigned
              rhn-support-kboone Kevin Boone
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: