[jboss-jira] [JBoss JIRA] Commented: (JBPM-452) Refactor SchedulerThread.executeTimers() to execute Timers in seperate Transactions

[Ronald van Kuijk (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-452?page=comments#action_12341116 ] 
            
Ronald van Kuijk commented on JBPM-452:
---------------------------------------

Quartz is threaded and will most likely solve this.

> Refactor SchedulerThread.executeTimers() to execute Timers in seperate Transactions
> -----------------------------------------------------------------------------------
>
>                 Key: JBPM-452
>                 URL: http://jira.jboss.com/jira/browse/JBPM-452
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM 3.0.1
>            Reporter: Rainer Alfoeldi
>         Assigned To: Tom Baeyens
>
> SchedulerThread.executeTimers() executes in a single transaction. 
> All Timers execute() methods are called in this transaction and the changes to the Timers themselves are persisted in this transaction.
> The failure of any one of the transacted resources in any one of the Timers would roll back all changes (workflow state as well as application resources) made during this call and we would effectively be where we started (probably running into the same failure the next time executeTimers() is called.)
> The use of a single transaction seems to be intentional (http://jira.jboss.com/jira/browse/JBPM-46  where Tom states that "we only use one transactional resource (jdbc connection) so ..."
> As we are talking about potentially thousands of Timers executing in a single transaction this doesn't seem to be viable.

-- 
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