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
Summary: [GSS](6.4.z) Initial calculation of the first expiration time for a scheduled...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.2.0,6.2.1,6.3.0,6.2.2,6.2.3,6.2.4,6.3.1,6.4.0,6.3.2,6.3.3,6.3.4,6.4.1,6.4.2,6.4.3,6.4.4,6.4.5,6.4.6
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: CR1
: EAP 6.4.7
Assignee: Ivo Studensky
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks: eap647-payload 1299882
TreeView+ depends on / blocked
 
Reported: 2016-01-14 16:32 UTC by wfink
Modified: 2019-09-12 09:45 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 1299882 (view as bug list)
Environment:
Last Closed: 2017-01-17 12:02:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-2799 0 Major Closed Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set 2017-05-11 03:03:22 UTC
Red Hat Issue Tracker WFLY-5995 0 Major Resolved Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set 2017-05-11 03:03:22 UTC
Red Hat Knowledge Base (Solution) 2136861 0 None None None 2016-01-22 22:25:44 UTC

Description wfink 2016-01-14 16:32:41 UTC 
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.
Comment 1 JBoss JIRA Server 2016-01-14 17:17:59 UTC 
Wolf-Dieter Fink <wolfdieter.fink> updated the status of jira WFLY-5995 to Coding In Progress
Comment 4 JBoss JIRA Server 2016-01-21 11:22:14 UTC 
Ivo Studensky <istudens> updated the status of jira JBEAP-2799 to Resolved
Comment 6 Jiří Bílek 2016-03-02 12:57:46 UTC 
Verified with EAP 6.4.7.CP.CR2.
Comment 7 JBoss JIRA Server 2016-06-14 11:36:59 UTC 
Jiri Pallich <jpallich> updated the status of jira JBEAP-2799 to Closed
Comment 8 Petr Penicka 2017-01-17 12:02:07 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Note You need to log in before you can comment on or make changes to this bug.