One solution that helps is to have a @Destroy method in which you cancel the
timer using timer.cancel().
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080151#4080151
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=40801
to elaborate, I want exactly one of these running for the application.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080128#4080128
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080128
Thanks Michael. I don't really want it to be persistent, because my
application-scoped Seam component is going to unknowingly create another the
next time I restart/redeploy. Is there some way to uniquely identity the
timer, so on start up if finds the record?
View the original post :
http:/
I am not sure about EJB3 timer. But I just want to add that the Quartz timer
can now be persistent or in-memory. Just configure a DB in the
seam.quartz.properties file if you need it to be persistence.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080121#408
Same issue. I couldn't figure out why my async method was being called so many
times. Any idea of how truncate that table on startup?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080119#4080119
Reply to the post :
http://www.jboss.com/index.html?module=b
Yes, I will wait for 1.3.0
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054579#4054579
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054579
___
jboss-user mailing list
jbos
tuxzilla, I'm doing exactly the same thing, and having the same problem.
Take a look at your \JBOSS_HOME\server\default\data\hypersonic dir. You will
find a file named localDB.log
Open this file. You will see something like this:
| After the first deploy:
| INSERT INTO TIMERS
VALUES('1','
ok. any idea when Seam 1.3 will GA?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052755#4052755
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052755
___
jboss-user mailing
Right, EJB timers are persistent.
In Seam 1.3 we give you a choice b/w (persistent) EJB timers and
(non-persistent) java.util.concurrent timers.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052727#4052727
Reply to the post :
http://www.jboss.com/index.htm
