>Is there a cause, why this is not made out-of-the-box?
I do not know. Maybe the example just tested on the hypersonic db. Anything
else is fun for your own exploration.
Justin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066999#4066999
Reply to the post
I got the same problem with ejb timer (can not get picked up after jboss
restarts). After adding the SLSB to jboss.xml descriptor everything works fine.
Is there a cause, why this is not made out-of-the-box?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40668
@supterlobster: would you explain, what changes you made? Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066878#4066878
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066878
Also, following problems:
1. Timer can not get picked up after jboss restarts.
The TimerServiceBean jndi name keeps changing between jboss restarts. Then
the old timer with obosolete timers.targetid will be ignored. Have to change
the local jndi name to fix it. Although it is not a big deal,
If using an ejb timer, what happens if one node goes down? My expericence is if
still have any running nodes, the timers local to the failed node will not be
picked up, since timer is local.
If it is true, ejb timer approach for jbpm is really in trouble.
Justin
View the original post :
http:
In jBPM 3.1, multiple scheduler threads query and execute timers without
synchronization, leading to duplicate executions.
In 3.2, this issue is effectively being addressed through a lock mechanism at
the database level. You should be able to run multiple job executor threads.
This mechanism is
Thanks for the info.
Yes, we would like to have the timer thread (servlet) running on each machine
in the cluster. It seems like the simplest approach.
When you say we will be in trouble doing this, are you doing so in the context
of 3.2? It looks like the issue is being addressed in JobExecut
It depends on how you have the timer thread/service/whatever deployed. If you
have one running for every server in the cluster, then yes, it will be an issue.
What we did, is only have ONE server run the timer thread/service, so they only
get run from one source to ensure there is no cluster mi
