Bug 1261895 - Metrics are not properly updated/refreshed in RHQ UI
Summary: Metrics are not properly updated/refreshed 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
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1261890
TreeView+ depends on / blocked
 
Reported: 2015-09-10 12:03 UTC by bkramer
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description bkramer 2015-09-10 12:03:32 UTC
Description of problem:
Metric values in Resource:Measurements and Group:Metrics portlets are not properly refreshed.

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

How reproducible:
Always

Steps to Reproduce:
1. Install RHQ 4.12 + EAP Plugins;
2. Navigate to RHQ UI -> Administration -> Metric Collection Templates -> JBossAS7 Standalone Server -> edit metric collection to set "Maximum Request Time" metric to 30 seconds;
3. Open two sessions of RHQ UI in the browser;
4. In the first one navigate to AutoGroup - JBossAS7 Standalone Servers -> Summary -> Activity and observe "Maximum Request Time" metric value;
5. In the second window navigate to the same AutoGroup - JBossAS7 Standalone Servers -> click on "Maximum Request Time" name/link -> click on 4h -> click on 1 h -> close this window;
6. Observe the value for "Maximum Request Time" - most likely it's changed;
7. Go back to the first window and confirm that initial value is not changed.
8. Press little refresh button in the right corner of the portlet and confirm that the value is not changed;
9. Request browser refresh -> confirm that metric value is changed.

Actual results:
Metric values are not refreshed in timely manner;

Expected results:
Metric values are regularly refreshed/updated;

Additional info:


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