0 Replies Latest reply on Jan 15, 2010 6:01 PM by Joel Monkey

    Job execution exception handling in a JTA environment

    Joel Monkey Newbie

      We have a jBPM workflow that executes custom activities implemented as session EJBs. Upon failure of one of these activities, the enclosing JTA transaction enters into an aborted state.   The {{ExecuteJobCmd}} seems to deal with exeptions by executing a {{JobExecutionHandler}} once the current transaction completes. This sequence is assured by the following:




      Unfortunately, since the JTA transaction has already been marked for rollback, this call fails!


      The question is, are we looking at a bug that only appears when using JTA transactions ({{org.jbpm.pvm.internal.tx.StandardTransaction}} doesn't care if the transaction is being aborted.) Or are we not scoping our JTA transactions properly?