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 1355796 - Incorrect value for "Store Percent Usage" metric shown in RHQ UI
Summary: Incorrect value for "Store Percent Usage" metric shown in RHQ UI
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1355793
TreeView+ depends on / blocked
 
Reported: 2016-07-12 14:37 UTC by bkramer
Modified: 2016-07-12 14:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


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

Description bkramer 2016-07-12 14:37:19 UTC
Created attachment 1178930 [details]
screen shots that show difference between value reported in RHQ and hawtio

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

Version-Release number of selected component (if applicable):
RHQ 4.12


How reproducible:
Always

Steps to Reproduce:
1. Install and start RHQ;
2. Install ActiveMQ in library mode using apache-activemq-5.xxxxx.zip located at $AMQ-HOME/extras;
3. Run the following to create new instance:

    $ /bin/activemq create instanceA

4. Let RHQ discover newly created instanceA and add it to the RHQ inventory;
5. Update files: users.properties, groups.properties and jetty-realm.properties (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 RHQ; 

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

Expected results:
Both hawtio and RHQ 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[10.33.24.105:39080]] (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 <<]]
****************************************************

or:

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


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