[ http://jira.jboss.com/jira/browse/JBPM-713?page=comments#action_12340027 ] Ronald van Kuijk commented on JBPM-713: --------------------------------------- Ryan, can you elaborate on this? You mean scheduling them and having them fired all at once? That would mean the scheduler has to be multi threaded... Maybe a good moment to try to switch to quartz for the scheduling -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-713?page=all ] Tom Baeyens closed JBPM-713. ---------------------------- Fix Version/s: jBPM 3.2 alpha 2 (was: jBPM 3.2) Resolution: Done this should be fixed with the new implementation. there is a new configuration in the processdefinition.xml for timers and asynchronous continuations : async="exclusive". All jobs that are exclusive for a given process instance will be executed in a serialized fashion by the same thread. For non-exclusive jobs, it will be possible that they are executed by multiple threads as the JobExecutor can have multiple threads. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira