Check if transaction is active before performing save operations ---------------------------------------------------------------- Key: JBPM-2983 URL: https://jira.jboss.org/browse/JBPM-2983 Project: jBPM Issue Type: Bug Security Level: Public(Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.9 Environment: Seam Reporter: Marek Novotny Assignee: Alejandro Guizar Labels: jbpm3, save, seam, transaction Fix For: jBPM 3.2.x Original Estimate: 4 hours Time Spent: 5 hours, 16 minutes Remaining Estimate: 0 minutes If task ending is unsuccessful, the BusinessProcessInterceptor.afterInvocation method will close the JbpmContext. However, there is an issue with jBPM auto-save operations, which complain about the transaction not being active and throw an exception. The exception in fact comes from Hibernate. jBPM should check whether the transaction is active before proceeding to perform the auto-save operations.

Check if transaction is active before performing save operations ---------------------------------------------------------------- Key: JBPM-2983 URL: https://jira.jboss.org/browse/JBPM-2983 Project: jBPM Issue Type: Bug Security Level: Public(Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.9 Environment: Seam Reporter: Marek Novotny Assignee: Alejandro Guizar Labels: jbpm3, save, seam, transaction Fix For: jBPM 3.2.10 Original Estimate: 4 hours Time Spent: 5 hours, 16 minutes Remaining Estimate: 0 minutes If task ending is unsuccessful, the BusinessProcessInterceptor.afterInvocation method will close the JbpmContext. However, there is an issue with jBPM auto-save operations, which complain about the transaction not being active and throw an exception. The exception in fact comes from Hibernate. jBPM should check whether the transaction is active before proceeding to perform the auto-save operations.