Red Hat Bugzilla – Bug 1298651
[GSS](6.4.z) Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set
Last modified: 2017-01-17 07:02:07 EST
Description of problem:
If a scheduled timer should be created with the following parameters:
ScheduleExpression[second=0 minute=0/5 hour=20-22 dayOfWeek=* dayOfMonth=* month=* year=* start=Thu Jan 14 09:45:35 GMT+1 2016]
The first schedule should be
Thu Jan 17 20:00:20 GMT+1 2016
but is calculated as
Sun Jan 17 20:45:35 GMT+1 2016
The minutes are not correctly set according to the schedule.
This happen for seconds/minutes if the ScheduleExpression limit the range.
Wolf-Dieter Fink <firstname.lastname@example.org> updated the status of jira WFLY-5995 to Coding In Progress
Ivo Studensky <email@example.com> updated the status of jira JBEAP-2799 to Resolved
Verified with EAP 6.4.7.CP.CR2.
Jiri Pallich <firstname.lastname@example.org> updated the status of jira JBEAP-2799 to Closed
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.