Bug 1059914 - [GSS] (6.2.x) @Schedule EJB Timer not using timezone when calculating next timeout
Summary: [GSS] (6.2.x) @Schedule EJB Timer not using timezone when calculating next ti...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.2
Assignee: Brad Maxwell
QA Contact: Jan Martiska
Russell Dickenson
URL:
Whiteboard:
Depends On: 1059911
Blocks: eap62-cp02-blockers
TreeView+ depends on / blocked
 
Reported: 2014-01-30 23:03 UTC by Brad Maxwell
Modified: 2018-12-05 17:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 1059911
Environment:
Last Closed: 2014-06-02 12:50:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2840 0 Major Resolved @Schedule EJB Timer not using timezone when calculating next timeout 2016-01-22 07:31:39 UTC

Description Brad Maxwell 2014-01-30 23:03:32 UTC
+++ This bug was initially created as a clone of Bug #1059911 +++

With a system running in Central Timezone, if it uses the annotation below specifying the timezone as Eastern timezone, with the hour set to the current hour.
The timer will fire once, and it will calculate the next timeout to be in the next hour CST, where as it should take in consideration the timezone specified on @Schedule which is Eastern. If it did, then the timer should continue to fire every minute.

  @Schedule(persistent = false, timezone = "America/New_York", dayOfMonth = "*", dayOfWeek = "*", month = "*", hour = "22", minute = "*", second = "0", year = "*")

21:53:00,006 INFO [stdout] (EJB default - 1) ScheduleTest: nextTimeout:Wed Jan 29 22:00:00 CST 2014

import javax.ejb.Schedule;
import javax.ejb.Singleton;
import javax.ejb.Startup;

@Startup
@Singleton
public class ScheduleTest {
  @Schedule(persistent = false, timezone = "America/New_York", dayOfMonth = "*", dayOfWeek = "*", month = "*", hour = "22", minute = "*", second = "0", year = "*")
  public void helloWorld(Timer time) {
    System.out.println("ScheduleTest: timer:" + time.getClass().getName() + " " + time.getNextTimeout() + " " + time.getInfo());
  }
}

Comment 1 JBoss JIRA Server 2014-02-06 06:46:53 UTC
Brad Maxwell <bmaxwell> updated the status of jira WFLY-2840 to Coding In Progress

Comment 4 Scott Mumford 2014-02-27 05:37:41 UTC
This bug has been marked for inclusion in the 6.2.2 Release Notes.

To meet a PM request to have a draft of the document available for review by 4th March 2014, ECS requires assistance from someone involved with it's resolution.

If someone could review the Doc Text field above and fill out any blanks and/or correct any inaccuracies, a draft can be completed in a timely manner.

Comment 5 Jan Martiska 2014-03-04 13:13:13 UTC
Verified in 6.2.2.CR2.

Comment 6 Scott Mumford 2014-03-21 00:46:20 UTC
Thanks for the draft text Brad.

Doc text rewritten to align more closely with other entries. Marking for inclusion in the final document.


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