Bug 909155 - Error message when setting start date = 00:00 and end date = 24:00
Summary: Error message when setting start date = 00:00 and end date = 24:00
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: DR01
: JON 3.2.1
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-08 12:25 UTC by bkramer
Modified: 2018-12-03 18:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 909160
: 909160 (view as bug list)
Environment:
Last Closed: 2014-05-08 17:44:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot showing the issue. (153.14 KB, image/png)
2013-02-08 12:25 UTC, bkramer
no flags Details

Description bkramer 2013-02-08 12:25:11 UTC
Created attachment 695043 [details]
screen shot showing the issue.

Description of problem:
JON throws Global uncaught exception when setting start date field = "00:00" and end date = "24:00". This message is not clear and we should provide more precise error message

Version-Release number of selected component (if applicable):
JON 3.1

How reproducible:
Always

Steps to Reproduce:
1. navigate to resource -> Monitoring tab -> press Advanced button -> enter incorrect start/end date/time -> for instance (02/08/2013 00:00 and 02/08/2013 24:00)
2.
3.
  
Actual results:
Globally uncaught exception at the top of the window

Expected results:
We should have more precise error message.

Additional info:

Comment 1 Jay Shaughnessy 2013-02-27 20:17:37 UTC
I wasn't able to reproduce this.  For me bad time ranges generated the expected warnings about begin time before end time.  I suggest this be re-tested after the charting updates are merged in, as perhaps this was fixed already, or perhaps those charting changes have updated the range selection logic.

Comment 2 Heiko W. Rupp 2013-08-12 09:29:04 UTC
This is now broken in a different sense:
if you enter 24:00 the widget automatically resets the date to 23:00.
Similar for 24:32 which resets to 23:32

Assigning to Mike as he is working on this right now

Comment 4 Mike Thompson 2014-01-28 14:40:15 UTC
This is the behavior of the TimeItem control. The isomorphic guys treat 24:00 as an out of bounds value and always move the hours beyond 23 back to 23. The largest valid value for the TimeItem is 23.59. This can be evidenced in this case: http://forums.smartclient.com/showthread.php?t=28868&highlight=timeItem+validation

I will need to use a different control other than TimeItem.

Comment 5 Mike Thompson 2014-01-30 02:03:53 UTC
Committed to master: 6a73a05

Replaced the TimeItem that allowed a 24:XX time format with two spinnerItems that control each domain independently 0-23 and 0-59.

@jkremser can you review and check into release branch for jon3.2.1?

Comment 6 Jirka Kremser 2014-01-30 13:05:26 UTC
commit in release branch: 8c9d2ac39

Comment 7 Simeon Pinder 2014-02-18 15:08:32 UTC
Moving to ON_QA as available for testing in the following brew build:
https://brewweb.devel.redhat.com//buildinfo?buildID=336752

Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA.  How this will be delivered to customers is still being discussed.

Comment 8 Mike Foley 2014-02-19 14:54:45 UTC
Verified JON 3.2.1.  "Advanced" button has changed to "Custom" ... new spinner controls do not allow for invalid ranges.

Comment 9 Mike Foley 2014-05-08 17:44:06 UTC
JON 3.2.1 released week of 5/5/2014


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