Really a question for the jBPM experts on the jBPM forum.
hi, i have the same problem, did you find a solution?
I put in a
workaround, which I don't like, which catches the original exception and then gets the JbpmContext's Hibernate session and clears the session.
I don't like it, but I'm not sure what else to do.
Lastly, I have the exact opposite problem when the jBPM persistence logic throws an exception ( like OptimisticLockException ). The jBPM rolls back, but the Seam initiated CMT doesn't.