ejb timer sometimes doesn't get cancelled when ejb is undeployed.
-----------------------------------------------------------------
Key: GERONIMO-623
URL: http://issues.apache.org/jira/browse/GERONIMO-623
Project: Geronimo
Type: Bug
Components: OpenEJB
Versions: 1.0-M3
Reporter: David Jencks
Assigned to: David Jencks
In some unknown circumstances an ejb timer can not get cancelled and continues
firing even after the ejb has been undeployed. This results in a stack trace
like this:
23:18:26,695 INFO [TransactionalExecutorTask] Exception occured while running
user task
java.lang.RuntimeException: Dead proxy for ejb
geronimo.server:EJBModule=modulename.jar,J2EEApplication=appName,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=ejbName
at
org.openejb.timer.BasicTimerServiceImpl.getTimerById(BasicTimerServiceImpl.java:204)
at
org.openejb.timer.BasicTimerServiceImpl$EJBInvokeTask.run(BasicTimerServiceImpl.java:256)
at
org.apache.geronimo.timer.TransactionalExecutorTask.run(TransactionalExecutorTask.java:57)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:552)
I'm going to put in some temporary hacks to BasicTimerServiceImpl so this
message only gets printed once even though the timer keeps firing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
