Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1355793 - Incorrect value for "Store Percent Usage" metric shown in JBoss ON UI
Summary: Incorrect value for "Store Percent Usage" metric shown in JBoss ON UI
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.3.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Michael Burman
QA Contact: Mike Foley
Depends On: 1355796
TreeView+ depends on / blocked
Reported: 2016-07-12 14:33 UTC by bkramer
Modified: 2016-07-14 09:30 UTC (History)
0 users

Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-07-14 09:30:37 UTC
Type: Bug

Attachments (Terms of Use)
screen shots that show difference between value reported in JBoss ON and hawtio (deleted)
2016-07-12 14:33 UTC, bkramer
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2438681 None None None 2016-07-13 10:43:40 UTC

Description bkramer 2016-07-12 14:33:22 UTC
Created attachment 1178916 [details]
screen shots that show difference between value reported in JBoss ON and hawtio

Description of problem:
JBoss ON UI shows 500% for "Store Percent Usage" while ActiveMQ hawtio shows 5.

Version-Release number of selected component (if applicable):
JBoss ON 3.3.5

How reproducible:

Steps to Reproduce:
1. Install and start JBoss ON;
2. Install ActiveMQ in library mode using located at $AMQ-HOME/extras;
3. Run the following to create new instance:

    $ /bin/activemq create instanceA

4. Let JBoss ON discover newly created instanceA and add it to the JBoss ON inventory;
5. Update files:, and (located in $AMQ-HOME/conf folder) to enable user (for instance admin:admin);
6. Change $AMQ-HOME/conf/activemq.xml file and reduce storageUsage from 100gb to 512mb (for instance);
7. Restart activeMQ;
8. Send big number of messages to this broker and monitor the value of the "Store Percent Usage" in hawtio and JBoss ON; 

Actual results:
Hawtio shows correct value (for instance 5) while JBoss ON shows 100 times of the value in hawtio (500)

Expected results:
Both hawtio and JBoss ON show the same value.

Additional info:
Attached screen shots.
Also, the agent.log file showed that Fuse plugin sends correct value:

2016-07-12 14:32:28,145 DEBUG [WorkerThread#0[]] (enterprise.communications.command.server.CommandProcessor)- {CommandProcessor.executed}Executed command - response is [Command Response: isSuccessful=[true]; command=[null]; results=[[MeasurementDataNumeric[name=TotalMessageCount, value=0.0, scheduleId=327207, timestamp=1468330348144], MeasurementDataNumeric[name=StoreLimit, value=5.36870912E8, scheduleId=327196, timestamp=1468330348144], MeasurementDataNumeric[name=TotalConsumerCount, value=0.0, scheduleId=327200, timestamp=1468330348144], MeasurementDataNumeric[name=TempPercentUsage, value=0.0, scheduleId=327199, timestamp=1468330348144], MeasurementDataNumeric[name=StorePercentUsage, value=5.0, scheduleId=327197, timestamp=1468330348144], MeasurementDataNumeric[name=TempLimit, value=5.36870912E8, scheduleId=327198, timestamp=1468330348144], MeasurementDataNumeric[name=MemoryPercentUsage, value=0.0, scheduleId=327194, timestamp=1468330348144], MeasurementDataNumeric[name=TotalEnqueueCount, value=0.0, scheduleId=327203, timestamp=1468330348144], MeasurementDataNumeric[name=TotalDequeueCount, value=0.0, scheduleId=327201, timestamp=1468330348144], MeasurementDataNumeric[name=MemoryLimit, value=7.20791142E8, scheduleId=327193, timestamp=1468330348144]]]; exception=[>> exception was null <<]]


MeasurementDataNumeric[name=StorePercentUsage, value=5.0, scheduleId=327197, timestamp=1468330348144]

Comment 2 bkramer 2016-07-14 09:30:37 UTC
Closing this with status "NOTABUG" as this is not JON issue but A-MQ plugin bug reported in:

Note You need to log in before you can comment on or make changes to this bug.