Bug 640554

Summary: Call-Time metric display range (within a date range) not saved
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: CallTimeAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: low    
Version: 4.0.0CC: ccrouch, jshaughn
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-27 20:50:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 639426, 678340    
Attachments:
Description Flags
server log none

Description Rajan Timaniya 2010-10-06 10:31:22 UTC
Created attachment 451860 [details]
server log

Description of problem:
Call-Time metric display range (within a date range) not saved.

Version-Release number of selected component (if applicable):
RHQ-Master build #378
http://hudson-qe.rhq.rdu.redhat.com:8080/view/RHQ/job/ci-rhq-master/378/

How reproducible:
Always

Steps to Reproduce:
1) Install RHQ server and agent (agent box should contain Jboss AS, Apache vhosts)
2) Log-in to RHQ
3) Enable call-time for war (ROOT.war)
4) Select Jboss AS and go to 'Monitoring->Call Time'
5) Click on 'Advanced Setting ...' 
6) Select 'Within a date range', provide from/to date and click on 'Ok' button
7) Apply metric settings
8) Again click on 'Advanced Setting ...'  and observe 'Display Range Settings'
  
Actual results:
Call-Time metric display range (within a date range) not saved.

Expected results:
Call-Time metric display range (within a date range) should be saved and also metric should display accordingly.

Additional info:
Please refer attached server log.

Comment 1 Ian Springer 2011-02-17 19:46:35 UTC
Note, this is JSF/portal-war and so will probably not be addressed.

Comment 2 Jay Shaughnessy 2014-06-27 20:50:28 UTC
outdated, new gui