-
1. Re: Asynchronous method triggered multiple times.
damianharvey Dec 6, 2007 4:27 AM (in response to vfaid)Are you using the hot deploy? I get the same thing happening with my Quartz events. The hot deploy effectively doesn't deregister the old event and also adds a new event.
Do you find that doing a full undeploy/reploy makes the event fire only once?
Cheers,
Damian. -
2. Re: Asynchronous method triggered multiple times.
vfaid Dec 6, 2007 11:04 AM (in response to vfaid)No, I'm not using hot deploy. Anyway, I've the problem both with Quartz and TimerService.
-
3. Re: Asynchronous method triggered multiple times.
vfaid Dec 7, 2007 8:58 AM (in response to vfaid)@damianharvey:
Sorry, you had right. The calls were due to EJBTimer timeout's that was saved by JBoss during previous deployment. Is it a bug of JBoss? -
4. Re: Asynchronous method triggered multiple times.
pmuir Dec 9, 2007 6:44 AM (in response to vfaid)No, this is a feature of EJB3 timer - read a book or the spec!
Quartz or the Java SE timer are non-persistent by default. -
5. Re: Asynchronous method triggered multiple times.
vfaid Dec 10, 2007 9:59 AM (in response to vfaid)I know that EJB3 Timer is persistent but is-it normal that JBoss add new timeout in its database each times the application is deployed?
I haven't the problem with Glassfish. -
6. Re: Asynchronous method triggered multiple times.
jakec Dec 11, 2007 8:35 PM (in response to vfaid)Is possible to use @Asynchronous to create a non-persistent timer? I know it is an RTFM, but I can't find the right M to RTF. :-( All I ever see is "EJB3 Timers persist by default", but nothing on how to override that default behavior.
-
7. Re: Asynchronous method triggered multiple times.
pmuir Dec 16, 2007 4:51 PM (in response to vfaid)vfaid, ask in the EJB3 forum
JakeC - not with the EJB3 timer, but it is with the Quartz timer.