[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1775) verify if collection exceptionHandlers can be loaded lazy
[
https://jira.jboss.org/jira/browse/JBPM-1775?page=com.atlassian.jira.plug...
]
Mark Torres commented on JBPM-1775:
-----------------------------------
This is causing issues on an app that I'm working on that uses seam.
We are using
<field name="isTransactionEnabled"><false/></field>
and this is causing isAbleToHandleExceptions to always return true, even if the jta
transaction is already rolledback. GraphElement proceeds to fetch the exceptionHandlers
lazily and throws jta resource exception, instead of the original exception.
verify if collection exceptionHandlers can be loaded lazy
---------------------------------------------------------
Key: JBPM-1775
URL: https://jira.jboss.org/jira/browse/JBPM-1775
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Tom Baeyens
Assignee: Alejandro Guizar
Fix For: jBPM 3.3.1 GA
From Martin Putz:
"
A quick test showed that setting all those relations to lazy="true" cuts down
the number of executed SQL selects quite drastically.
I don't see any negative side effects of changing these settings, but I'm curious
about the reasons why lazy="false" is chosen as default. Especially as I
don't see a lot of our customers using exception handlers (or at least they don't
report it).
Regards,
Martin
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira