-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 7.5.0.redhat
-
Fix Version/s: 7.5.1.redhat
-
Component/s: ActiveMQ Plugin
-
Labels:None
-
Environment:
JBoss A-MQ Broker Queue deployed;
Store Percent Usage measurement collection is enabled;
Steps to Reproduce:
1. Deploy A-MQ broker queue.
2. From JBoss ON, discover and import A-MQ resources.
3. Enable Store Percent Usage metric for discovered queues.
4. Send messages to the queue so that they are stored in the ActiveMQ store space.
5. From JBoss ON UI, refresh metric page containing queues metrics and notice that the Live Value column is 100 times larger then the value displayed in the Fuse Management Console.JBoss A-MQ Broker Queue deployed; Store Percent Usage measurement collection is enabled; Steps to Reproduce: 1. Deploy A-MQ broker queue. 2. From JBoss ON, discover and import A-MQ resources. 3. Enable Store Percent Usage metric for discovered queues. 4. Send messages to the queue so that they are stored in the ActiveMQ store space. 5. From JBoss ON UI, refresh metric page containing queues metrics and notice that the Live Value column is 100 times larger then the value displayed in the Fuse Management Console.
The activemq-plugin-7.5.0.redhat-621070.jar management plug-in appears to have a bug in it that is causing the "Store Percent Usage" measurement to be 100 times larger then what it really is.
Similar issue has been reported for the "Memory Percent Usage" metric (see https://issues.jboss.org/browse/FUSEJON-97) and this seems to be fixed already.
I didn't check "Temp Percent Usage" measurement - but it is most likely that we need to fix the value plugin returns for this metric too.
This bug is referenced in knowledge solution: https://access.redhat.com/solutions/2438681. There is no workaround at this time.
