jBPM5 is not very friendly when it comes to timers :-( All your sessions have to be loaded from persistence for their timers to expire. So it is up to you to write some special code to load all your sessions when JBoss starts.
More information here:
Hi, I've been absent
After reading this https://community.jboss.org/thread/211785 i have idea:
I have about 500,000 active instances of processes. Each instance of the process is supported by a single session.
loadStatefulKnowledgeSession (...) from database takes 150ms.
After restart AS is: 500 000 * 0,15 / 60 / 60 is about 20 hours. This is a joke
6 years ago in jbpm 3.2.2 was simple mechanism with one table in the database and select to them every 1 second. Simple but very effective.
Today we have version 5.3 and it does not work? I can not belive it. I have to write my implementation?
Is the problem (for web BPMN designer): Catching Itermediate Events, Start Events and Throwing Intermediate Events?
is there any way to work with timers without load session?