Bug 640554 - Call-Time metric display range (within a date range) not saved
Summary: Call-Time metric display range (within a date range) not saved
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: CallTime
Version: 4.0.0
Hardware: All
OS: Linux
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: gwt-iframes jon3
TreeView+ depends on / blocked
 
Reported: 2010-10-06 10:31 UTC by Rajan Timaniya
Modified: 2014-06-27 20:50 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2014-06-27 20:50:28 UTC


Attachments (Terms of Use)
server log (356.71 KB, text/x-log)
2010-10-06 10:31 UTC, Rajan Timaniya
no flags Details

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


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