-
Bug
-
Resolution: Done
-
Major
-
jBPM 3.2.9
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.
- relates to
-
JBPAPP-5517 Seam exception and transaction handling in JBPM integration is not correct for failed EL expression evaluation
- Closed
-
JBPM-3883 Fix for JBPM-2983 broke externally managed transactions support
- Closed