+++ 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()); } }
Brad Maxwell <bmaxwell> updated the status of jira WFLY-2840 to Coding In Progress
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.
Verified in 6.2.2.CR2.
Thanks for the draft text Brad. Doc text rewritten to align more closely with other entries. Marking for inclusion in the final document.