[
https://issues.jboss.org/browse/AS7-3119?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on AS7-3119:
------------------------------------
EJB EG Oct 31 2007:
{quote}
2. Overlapping timer callbacks
The original EJB Timer Service was aimed at modeling coarse-grained
business processes. The spec states that such events are expected to
correspond to hours, days, or longer periods of time. As such, it did
not fully specify the runtime behavior for some timer callback issues
that are more likely to arise with much finer-grained timeouts.
Namely, what happens if a callback for a repeating timer is still
processing when the next callback is scheduled to occur?
One aspect of this issue is whether it's ok to discard such pending
callbacks. Another is whether multiple overlapping callbacks for the
same timer should be delivered concurrently or sequentially.
One suggestion we discussed for handling part of the overlapping issue
is a "backlog" field that would specify the number of overlapping
callbacks to allow before the container begins to discard.
Another item worth mentioning is the EJB specification does address a
related issue regarding server crash/shutdown. If the container is not
running when a timer would have expired, the container is required to
invoke the timer's callback method during container restart. In the
case of an interval timer the current spec only requires the container
to deliver at least one missed expiration.
{quote}
Recurring timer might executed concurrent if the duration of the
timeout method will be longer than the interval
----------------------------------------------------------------------------------------------------------------
Key: AS7-3119
URL:
https://issues.jboss.org/browse/AS7-3119
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Beta1b
Reporter: Wolf-Dieter Fink
Assignee: Wolf-Dieter Fink
Labels: community, jboss7, timerservice
Timer with a short interval might be called before the previous execution is finished.
This concurrent execution might harm the Bean provider expectations and implementation.
In previous releases (AS5 EAP5) the execution is dropped in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira