Problem with long running async actions rolled back in jBPM 3.2

Issue

In a process, there is a timer that continues the process execution. The token correctly advances to the next node which includes the asynchronous execution of some actions. In the server.log file we can see that the token leaves node "Action_Node1" at 14:30:34 and that it enters node "Check_Result" at 14:42:46, but at 14:42:56 there is a rollback on the jta transaction. As a result, the token is back at the timer node and the actions are executed again, which is incorrect from the business perspective.

What is causing the hibernate transaction to be rolled back?