-
Bug
-
Resolution: Done
-
Major
-
5.5.0.Final
-
None
-
None
-
Low
I stumbled upon this while searching for a potential cause of JBPM-4132 .
In the method afterCompletion of JtaTransactionSynchronizationAdapter a call with STATUS_ACTIVE would cause an infinite loop. As this value in itself indicates an inconsistent state the error probably wasn't noticed earlier.