Author: ozizka(a)redhat.com
Date: 2009-08-21 19:36:59 -0400 (Fri, 21 Aug 2009)
New Revision: 685
Modified:
trunk/jsfunit/src/test/java/org/jboss/jopr/jsfunit/as5/jmsDestinations/JMSMetricsTest.java
Log:
* JMS - checkQueueMetricsAfterReceivingMessage() - Count value constraints diminished.
Modified:
trunk/jsfunit/src/test/java/org/jboss/jopr/jsfunit/as5/jmsDestinations/JMSMetricsTest.java
===================================================================
---
trunk/jsfunit/src/test/java/org/jboss/jopr/jsfunit/as5/jmsDestinations/JMSMetricsTest.java 2009-08-21
23:36:40 UTC (rev 684)
+++
trunk/jsfunit/src/test/java/org/jboss/jopr/jsfunit/as5/jmsDestinations/JMSMetricsTest.java 2009-08-21
23:36:59 UTC (rev 685)
@@ -548,13 +548,14 @@
expectedMetrics.put(DELIVERING_COUNT, "2");
expectedMetrics.put(MSG_COUNT, "2");
expectedMetrics.put(SCHEDULED_MSG_COUNT, "0");
- expectedMetrics.put(COUNT, "3");
+ // This value was sometimes 0, because the counter got reset -> commenting out.
+ // "The total message count since startup or last counter reset."
+ //expectedMetrics.put(COUNT, "3");
//expectedMetrics.put(COUNT_DELTA, "3");
expectedMetrics.put(DEPTH, "2");
//expectedMetrics.put(DEPTH_DELTA, "2");
- checkDestinationMetrics(jndiName, expectedMetrics, getQueueSummaryMetrics(),
- DestinationType.QUEUE);
+ checkDestinationMetrics(jndiName, expectedMetrics, getQueueSummaryMetrics(),
DestinationType.QUEUE);
}
/**
Show replies by date