XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • TBD EAP 5
    • EAP_EWP 5.1.1, EAP_EWP 5.1.2
    • Consoles, Messaging
    • RHEL6 rpm

    • N/A
    • Not Required

      Hello, admin console doesn't show JBM queue and topic metrics. It always shows message count being zero. I'm not sure about subscriber count. This value seems to be correct for the local subscribers but it doesn't represents subscribers on other cluster nodes.

      I was suspecting clustering is not working but it turned out it is only the console that doesn't. This is the exception I'm getting trying to obtain metrics in admin console:

      2011-09-23 15:53:12,209 ERROR [org.rhq.core.pc.measurement.MeasurementManager] (http-8080-14) Could not get measurement values
      java.lang.IllegalStateException: Failed to find [ComponentType{type=JMSDestination, subtype=Topic}] ManagedComponent named [TradeStreamerTopic].
              at org.rhq.plugins.jbossas5.ManagedComponentComponent.getManagedComponent(ManagedComponentComponent.java:365)
              at org.rhq.plugins.jbossas5.ManagedComponentComponent.getValues(ManagedComponentComponent.java:227)
              at sun.reflect.GeneratedMethodAccessor789.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:616)
              at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
              at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
              at java.util.concurrent.FutureTask.run(FutureTask.java:166)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
              at java.lang.Thread.run(Thread.java:636)

      See below the test topic definition I used:

      <?xml version="1.0" encoding="UTF-8"?>
      <server>
        <mbean code="org.jboss.jms.server.destination.TopicService"
            name="jboss.messaging.destination:service=Topic,name=TradeStreamerTopic"
            xmbean-dd="xmdesc/Topic-xmbean.xml">
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
            <depends>jboss.messaging:service=PostOffice</depends>
            <attribute name="JNDIName">TradeStreamerTopic</attribute>
            <attribute name="Clustered">true</attribute>
         </mbean>
         <mbean code="org.jboss.jms.server.destination.QueueService"
            name="jboss.messaging.destination:service=Queue,name=TradeBrokerQueue"
            xmbean-dd="xmdesc/Queue-xmbean.xml">
            <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
            <depends>jboss.messaging:service=PostOffice</depends>
            <attribute name="JNDIName">TradeBrokerQueue</attribute>
            <attribute name="Clustered">true</attribute>
         </mbean>
      </server>

      Here I wrote a sender webapp and a listener MDB I used to verify everything is working as expected:
      http://anonsvn.jboss.org/repos/qa/people/akostadi/mdbtest/
      http://anonsvn.jboss.org/repos/qa/people/akostadi/jmssender/

      run "mvn package" to generate the deployable archives and put in deploy directory.

              jtripath Jyoti Tripathi (Inactive)
              akostadi1@redhat.com Aleksandar Kostadinov
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: