It was a bug.
http://sourceforge.net/tracker/index.php?func=detailaid=1078243group_id=22866atid=376685
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858317#3858317
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858317
There isn't a crash in my example, my problem occurs while Jboss is starting.
Here are the steps I think Jboss works with my timers:
- Jboss deploys my application
- Jboss starts my application
- The ServletContext of my application is initialized
- My timers are created by my
Thank you for your reply.
I can change the ejb-deployer.xml file to avoid to store my timers in the
database, but then I don't know if the timers can be restored after crashes and
if they work in a cluster environment.
View the original post :
I've another problem with Timer Service, and I hope the last one.
I've launched automatically my Timer Service when my application starts, that
is in a Servlet Context Listener, as described in
http://radio.weblogs.com/0135826/2004/09/21.html.
I've noticed that my timer service is duplicated,
When my Ejb Timer Service expires, I get a warning message like this:
WARN [TimerImpl] Timer was not registered with Tx, reseting state:
[id=1target= ... ]
What is the problem?
I'm using JBoss 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418).
View the original post :
