I found some info here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ChangeTheDatabase
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047821#4047821
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4047821
Could some one put a link to where in the jboss wiki I can find out how to
disable the persistent timer queue? I can't seem to find it any where.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038216#4038216
Reply to the post :
+1 vote for decent timer service!
- should handle large numbers of timers
- timers should persist between restarts
- perhaps there could be a way to identify timers to overwrite on
redeployment (i.e. repeating timers)
View the original post :
You should hassle the EJB3 team about this. I agree that our timer service
could do with improvements. Let them know.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4004600#4004600
Reply to the post :
We disabled the persistent timer queue. It is explained in the JBoss Wiki how
to do that.
As far as I know, we still do have the Could not destroy component-problem
with any other bean, that is triggered using startup. No solution so far.
View the original post :
We are considering alternative implementations for timer events than the EJB
timer service. In the meantime, you are at the mercy of the timer service
implementation and it's capabilities.
I'm not familiar with the Could not destroy component problem.
View the original post :
I am experiencing the same issue - did you ever resolve this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003550#4003550
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4003550
Hi,
I tried to fix this by calling timer.cancel() during the destroy method, which
seems to me is the way to handle timers during shutdown if I don´t want them to
get persisted.
Now I´m having the Could not destroy component: componentName
EJBNoSuchObjectException: Could not find stateful
