During business central startup, timers were firing prior to business process deployment completion.
We have set the system property
org.jbpm.timer.delay to add a delay before Quartz starts.
We do not think this is a sustainable long-term solution. We picked a value that is not too long but probably long enough. As we add more deployments, we have two risks:
1. We forget about this setting until our deployments take more than the delay and it breaks.
2. We set it to a very high value which delays work for our users after a restart.
Red Hat JBoss BPM Suite (BPMS) 6.4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.