Description of problem: Metric values in Resource:Measurements and Group:Metrics portlets are not properly refreshed. Version-Release number of selected component (if applicable): JON 3.3.3 How reproducible: Always Steps to Reproduce: 1. Install JON 3.3.3 + EAP Plugins; 2. Navigate to JON 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 JON 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:
commit 9731418edd70d89ad411cf61412cf4fb1f7b5c56 Author: Ruben Vargas <rvargasp> Date: Wed May 11 12:38:54 2016 -0500 Bug 1261890 - Metrics are not properly updated/refreshed in JON UI
Moving to ON_QA as available to test with the following build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=502442 Note: jon-server-patch-3.3.0.GA.zip maps to JON 3.3.6(jon-server-3.3.0.GA-update-06.zip)
Executed required reproductive steps. Observed as expected: metric values are updated in timely manner.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1519.html