[
https://jira.jboss.org/browse/JBAS-8221?page=com.atlassian.jira.plugin.sy...
]
shanthosh yogamurugan commented on JBAS-8221:
---------------------------------------------
Here goes the explanation :
The timer service did save the next timeout but not the consecutive timeouts . If you
restore the timer with with one of the programmed schedule after the current time , the
timer restores perfectly.
Expired interval timers re-expire on restart
--------------------------------------------
Key: JBAS-8221
URL:
https://jira.jboss.org/browse/JBAS-8221
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.1.0.GA, 6.0.0.M1, 6.0.0.M2, 6.0.0.M3
Reporter: Shaun Appleton
Assignee: jaikiran pai
Attachments: EJBTimerServiceImpl.java, ExampleTimerBean.java, timerlogger.pdf
If you restart JBoss after an interval timer has expired it re-expires. This means the
timer is, in effect, called every timer the server is restarted.
The spec [section 18.4.2] states what should happen between a server crash and a restart
- "Any interval timers that have expired during the intervening time must cause the
timeout callback method to be invoked at least once upon restart."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira