Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1104194

Summary: globally uncaught exception while changing chart custom time
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: Monitoring -- Other, UIAssignee: Jirka Kremser <jkremser>
Status: CLOSED WORKSFORME QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2.1CC: jkremser, jshaughn, mfoley
Target Milestone: ER01   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-09 15:19:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
exception
none
server.log none

Description Armine Hovsepyan 2014-06-03 13:22:48 UTC
Created attachment 901786 [details]
exception

Description of problem:
globally uncaught exception while changing chart custom time from chart

Version-Release number of selected component (if applicable):
Version :3.2.0.GA Update 02 
Build Number :	055b880:0620403

How reproducible:
always

Steps to Reproduce:
1. navigate to resource having enabled measurement metrics
2. click on metric name from resource name -> summary -> Resource: Measurements
3. select time range from chart (mouse select)

Actual results:
globally uncaught exception

Expected results:
chart for custom time is visible

Additional info:
screenshot attached

Comment 1 Armine Hovsepyan 2014-06-03 14:50:10 UTC
Created attachment 901817 [details]
server.log

Comment 2 Armine Hovsepyan 2014-06-03 14:51:49 UTC
additional info:
issue appears after postgresql service restart -- see server.log
and can be fixed by rhqctl restart

making severity medium

Comment 4 Jirka Kremser 2014-08-22 13:13:21 UTC
I was not able to reproduce. I openned the popup with the metric, changed the time range by mouse (by dragging on the graph). No problems. Then I restarted postgres, have some exceptions in the server log, but unrelated to this issue and it is quite understandable, that there will be exceptions, if you kill the db, right?

Once the postgres was running again I did the same thing again. I.e. change the time range by mouse. Again no issues. Perhaps you restarted the postgres in some particular moment when it was trying to write/read something from the db. I think we can't guarantee the full functionality of RHQ/JON when admins restarts the db under the covers. 
It's like unplugging the electricity and then complaining the bulb is not on :]

Armine, could you please try to reproduce in ER1? I was not able to, perhaps it was fixed as a side effect of some other work, or it is not deterministic.

Comment 5 Armine Hovsepyan 2014-08-25 07:46:33 UTC
It is not visible in 3.3 ER1 - it must have been fixed by another fix.