[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2918) Problem when loading exceptionHandlers when transaction has been rolled back
[
https://jira.jboss.org/browse/JBPM-2918?page=com.atlassian.jira.plugin.sy...
]
Jens Augustsson commented on JBPM-2918:
---------------------------------------
Are you sure about the implemented patch? Because this doesn't solve the problem for
me, imho.
GraphElement#isAbleToHandleExceptions will always return true, because
#persistenceService.isTransactionActive || #isTransactionPresent will both return false.
So 'false' || !'false' == 'true'.
So when DbPersistenceService.transaction == null, #isAbleToHandleExceptions will return
true?
I /assume/ the patch
--return persistenceService.isTransactionActive()
-- || !persistenceService.isTransactionPresent();
++return persistenceService.isTransactionActive();
..would cut is for me?
br,
Jens
Problem when loading exceptionHandlers when transaction has been
rolled back
----------------------------------------------------------------------------
Key: JBPM-2918
URL: https://jira.jboss.org/browse/JBPM-2918
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Environment: Weblogic 10, JTA, EJB CMT
Reporter: Michel Rasschaert
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Attachments: jbpm-patch.txt, jbpm-patch2.patch, mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Our problem is exactly the same as [JBPM-681].
However the fix proposed in [JBPM-1775] is not working for us.
I will attach a patch that fixes the problem for us.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira