]
Amit Bafna commented on JBAS-5779:
----------------------------------
I am facing this issue as well. Any idea on timeline or a fix version?
Cheers!
Amit
EJB timers ignoring start date
------------------------------
Key: JBAS-5779
URL:
https://jira.jboss.org/jira/browse/JBAS-5779
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.3.GA
Reporter: Phil Haigh
Assignee: Dimitris Andreadis
I am using the EJB timer scheduler for some recurring tasks in my application. There are
3 of them, designed to run overnight, every night (i.e. every 24hours).
All works well when I deploy the application, and on subsequent deployments. However,
when I restart JBoss, the timers run every 24 hours after the RESTART, rather than the
proper scheduled time.
My timer table looks like:
Code:
select TIMERID, TARGETID, INITIALDATE, TIMERINTERVAL from TIMERS;
+---------------+-----------------------------------------------------------------------------------
--------------------+---------------------+---------------+
| TIMERID | TARGETID
| INITIALDATE | TIMERINTERVAL |
+---------------+-----------------------------------------------------------------------------------
--------------------+---------------------+---------------+
| 1215864788521 |
[target=jboss.j2ee:service=EJB3,ear=wildfrontiers.ear,jar=jboss-seam.jar,name=Time
rServiceDispatcher] | 2008-07-09 02:00:06 | 86400000 |
| 1215864788522 |
[target=jboss.j2ee:service=EJB3,ear=wildfrontiers.ear,jar=jboss-seam.jar,name=Time
rServiceDispatcher] | 2008-07-09 01:05:06 | 86400000 |
| 1215864788523 |
[target=jboss.j2ee:service=EJB3,ear=wildfrontiers.ear,jar=jboss-seam.jar,name=Time
rServiceDispatcher] | 2008-07-09 01:00:06 | 86400000 |
+---------------+-----------------------------------------------------------------------------------
--------------------+---------------------+---------------+
So, it I restart JBoss at 6pm, July 12th, the tasks will next run at 6pm July 13th,
rather than the expected 1am, 1.05am and 2am 13th July.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: