Hi!
According to ejb-3.0 spec (page 88) in @PreDestroy method in stateless bean
only following method are allowed:
- SessionContext methods: getBusinessObject, getEJBHome, getEJBLocalHome,
getEJBObject, getEJBLocalObject,getTimerService, lookup
- JNDI access to java:comp/env
-
i have found the solution :
I killed all timers associated with the current bean, for instance :
| //to be sure that there is not previous timer still running on JBOSS
| Collection timersList = timerService.getTimers ();
| for (Object timer: timersList) {
Hello,
- First I called the method registerTimer ().
- Secondly, I called the method unregisterTimer (), the method fails and the
timer is not killed.
- Third, I undeploy my ear, and deploy it again, the portion of log file shows
that the timer is still active:
| ...
|
| 2009-03-09
anonymous wrote : but this does not work, and the timer remains active even
after the bean is undeployed.
How did you verify this? Can you post the appropriate logs which show this
behaviour?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4214788#4214788
I'm sure the timer is not killed because I see in the logs that the timer is
still active.
i will post the log file in the afternoun.
Thank's.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4214876#4214876
Reply to the post :
Also please post the logs which show the undeployment itself, apart from the
logs after the undeployment.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4215112#4215112
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4215112
