[
https://jira.jboss.org/jira/browse/JBAS-7125?page=com.atlassian.jira.plug...
]
Jason T. Greene commented on JBAS-7125:
---------------------------------------
For jms message stats to work they have to be enabled. Also they are not always exactly in
sync with messages by their design. The time last update is the value of the last time
statistics were recorded, and the message count then. The delta is nothing but the
difference between the last call to read the delta, so this metric is not entirely
useful.
JMS Destinations: properties "Count" and "Time Last
Update" are 0 after sending a message
-----------------------------------------------------------------------------------------
Key: JBAS-7125
URL:
https://jira.jboss.org/jira/browse/JBAS-7125
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (JBoss Messaging), ProfileService
Affects Versions: JBossAS-5.1.0.GA
Environment: Tests:
testQueueMetrics*
testTopicMetrics*
Reporter: Ondrej Žižka
Assignee: Scott M Stark
Fix For: JBossAS-5.2.0.Beta1
After sending a message(s), some properties have bad values:
Count = 0,
Count Delta = 0,
Time Last Update = 0,
However,
Depth 4 The current message count of pending messages within the queue waiting for
dispatch
Depth Delta 3 The message count delta of pending messages since last method call
Did the meaning of Count change?
I've looked at the queue MBean in JMX console, and there's no count property.
Jopr takes this from ProfilseService, so perhaps that's where zero comes from? Anyway,
this is a regression.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira