AnsweredAssumed Answered

Finishing Tasks: Transaction Conflict after Upgrade (5.16.1-->5.18)

Question asked by benpr on Oct 8, 2015
Latest reply on Oct 8, 2015 by benpr
after upgrade to 5.18 we have two processes with transaction conflicts. All other processes works fine.
The system hangs after calling "formService.submitTaskFormData" until the lock timeout is over. Then the following errors occurs:
<blockcode>WARN  [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffc1646777:-4ff5cd70:56151b4f:5da1 in state  RUN
WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffc1646777:-4ff5cd70:56151b4f:5da1 invoked while multiple threads active within it.
WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffc1646777:-4ff5cd70:56151b4f:5da1 aborting with 1 threads active!
WARN  [org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorTrackingImpl] (Transaction Reaper Worker 0) HHH000451: Transaction afterCompletion called by a background thread; delaying afterCompletion processing until the original thread can handle it. [status=4]
WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffc1646777:-4ff5cd70:56151b4f:5da1</blockcode>

It's irrelevant which job engine (jobExecutor / asyncExecutor) is used.
The first problematical process fires a "runtimeService.signalEventReceived" to another process and this fails.
The second process is called via multi instance "call activity".

What can I do to fix the problem?

Regards,

Ben

Outcomes