Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8997

HornetQ message queue reports "There are currently no numeric metrics available." in admin-console metrics page

XMLWordPrintable

    • Hide

      1. Start EAP 5.1.2 all profile with HornetQ installed
      2. Navigate to http://localhost:8080/admin-console
      3. After log-in, from the navigation tree, expand and select localhost.localdomain / JBossAS Servers / JBoss EAP 5 (all) / JMS Manager / JMS Queues / jms.queue.DLQ
      4. Select the Metrics tab
      5. Repeatedly click the Refresh button until the issue occurs (normally a click every 3 or 4 seconds for a minute should do it)

      Show
      1. Start EAP 5.1.2 all profile with HornetQ installed 2. Navigate to http://localhost:8080/admin-console 3. After log-in, from the navigation tree, expand and select localhost.localdomain / JBossAS Servers / JBoss EAP 5 (all) / JMS Manager / JMS Queues / jms.queue.DLQ 4. Select the Metrics tab 5. Repeatedly click the Refresh button until the issue occurs (normally a click every 3 or 4 seconds for a minute should do it)
    • Release Notes
    • Hide
      When refreshing the metrics page of a HornetQ message queue, a message indicating that there were no numeric metrics available appeared occasionally. This was caused by a race condition identified in JBPAPP-9406. The race condition has been corrected to prevent the management view from becoming out-of-sync and the problem no longer occurs.
      Show
      When refreshing the metrics page of a HornetQ message queue, a message indicating that there were no numeric metrics available appeared occasionally. This was caused by a race condition identified in JBPAPP-9406 . The race condition has been corrected to prevent the management view from becoming out-of-sync and the problem no longer occurs.
    • Documented as Resolved Issue
    • NEW

      When browsing message queue metrics for a JMS Queue in admin-console, the Metrics page displays:

      Numeric Metrics

      There are currently no numeric metrics available.

      With DEBUG logging enabled, the following debug message is produced at the time this occurs:

      DEBUG [org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler] (http-0.0.0.0-8080-2) Call to [org.jboss.as.integration.hornetq.jopr.JMSQueueComponent.getValues()] with args [[org.rhq.core.domain.measurement.MeasurementReport@560399f8, [MeasurementScheduleRequest[scheduleId=1, name=getDeliveringCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getMessageCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getConsumerCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getMessagesAdded, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null], MeasurementScheduleRequest[scheduleId=1, name=getScheduledCount, interval=0, enabled=true, dataType=MEASUREMENT, rawNumericType=null]]]] failed.
      java.util.concurrent.ExecutionException: java.lang.NullPointerException
      at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
      at java.util.concurrent.FutureTask.get(FutureTask.java:119)
      at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:446)
      at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:434)
      at $Proxy193.getValues(Unknown Source)
      at org.rhq.core.pc.measurement.MeasurementManager.getRealTimeMeasurementValue(MeasurementManager.java:435)
      at org.jboss.on.embedded.bean.MeasurementUtils.loadMeasurementData(MeasurementUtils.java:126)
      at org.jboss.on.embedded.ui.MetricAction.view(MetricAction.java:107)
      ...
      Caused by: java.lang.NullPointerException
      at org.jboss.as.integration.hornetq.jopr.util.ManagementSupport.getOperation(ManagementSupport.java:40)
      at org.jboss.as.integration.hornetq.jopr.JMSResourceComponent.getValues(JMSResourceComponent.java:86)
      at sun.reflect.GeneratedMethodAccessor622.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)
      ... 1 more

      This issue does not happen all the time. It may take several click of the Refresh button over a period of time to reproduce the issue.

              rhn-support-loleary Larry O'Leary
              rhn-support-loleary Larry O'Leary
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: