there were some issues with 6.1.0 and spring local transactions that were already addressed. Do you mind checking 6.2.0.CR2 to see if all works well?
Thank you for the reply. I will test it on the 6.2.0.CR2 to check it further. Also, just wanted to know, if there is any way like by extending the AbstractRuntimeManager or providing the custom implementation for AbstractRuntimeManager to resolve the above issue in 6.1.0?
Also earlier, while using jBPM 5.4, i have seen that, the Potential Owner information of the task is automatically getting stored in peopleassignments_potowners table when we start the process. However, using the spring local transaction in jBPM 6.1.0 version, i can see that the task related data is not getting persisted in peopleassignments_potowners table and due to this the claim operation failing. It throws PermissionDeniedException. Is this also the known issue in jBPM 6.1.0?
I am facing same issue. Were you able to fix the issue on 6.1.0?