[
https://issues.apache.org/jira/browse/OPENEJB-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599840#comment-13599840
]
Romain Manni-Bucau commented on OPENEJB-2004:
---------------------------------------------
the issue is the fact we (ATM) can't unschedule persistent timers without
loosing them. Persistent timers need to be *paused* to be able to get them back
at next startup.
> EjbTimerService fails to shut down after recent changes
> -------------------------------------------------------
>
> Key: OPENEJB-2004
> URL: https://issues.apache.org/jira/browse/OPENEJB-2004
> Project: OpenEJB
> Issue Type: Bug
> Components: container system
> Affects Versions: (trunk/tomee)
> Environment: NA
> Reporter: Andy Gumbrecht
>
> EjbTimerService fails to shut down after recent changes made for persistent
> timers.
> The pausing of jobs rather than un-scheduling seems to block the first
> 'friendly' shutdown thread, causing the thread to wait for the defined
> timeout.
> This occurs synchronously, so multiple scheduler shut down calls can take an
> age to complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
