[jbpm-users] [JBoss jBPM] - Timers don't get executed after server crash

We've experiencing some problems regarding timers that don't get executed using jBPM version 3.2.2 after a server crash. It seems like that not alle timers are re-initiated after rebooting the application server (ver. 4.2.2). This is getting a quite critical issue since we have a lot of non-executed jobs in the jbpm_job table with old due dates. Is there any way to restart those triggers or to prevent this from happening? Our jboss.xml looks like this: <jboss> | <enterprise-beans> | | <session> | <ejb-name>CommandServiceBean</ejb-name> | <jndi-name>ejb/CommandServiceBean</jndi-name> | <local-jndi-name>CommandServiceBean</local-jndi-name> | </session> | | <session> | <ejb-name>TimerServiceBean</ejb-name> | <jndi-name>ejb/TimerServiceBean</jndi-name> | <local-jndi-name>TimerServiceBean</local-jndi-name> | </session> | | <message-driven> | <ejb-name>CommandListenerBean</ejb-name> | <destination-jndi-name>queue/JbpmCommandQueue</destination-jndi-name> | </message-driven> | | <message-driven> | <ejb-name>JobListenerBean</ejb-name> | <destination-jndi-name>queue/JbpmJobQueue</destination-jndi-name> | </message-driven> | | </enterprise-beans> | </jboss> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237932#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...