[esb-issues] [JBoss JIRA] Commented: (JBESB-1374) Exception handling problem when used integrated jBPM/ESB with JTA
[ http://jira.jboss.com/jira/browse/JBESB-1374?page=comments#action_12389567 ]
Kevin Conner commented on JBESB-1374:
-------------------------------------
Any RuntimeException caught by the ActionProcessingPipeline, whatever the source, will
cause a rollback (as will Error subclasses).
The responsibility for deciding whether a RuntimeException should be wrapped/unwrapped
lies within the jBPM and integration code. It is as valid for this code to choose to
respond to the originating service with a fault message as it would be to cause a JTA
rollback.
If this RuntimeException was resulting in an inconsistent state within the jBPM then I
would expect the jBPM code to call setRollbackOnly on the active transaction. As this
hasn't happened we can only assume that the jBPM state is consistent and that we
should honour their intentions.
Exception handling problem when used integrated jBPM/ESB with JTA
-----------------------------------------------------------------
Key: JBESB-1374
URL: http://jira.jboss.com/jira/browse/JBESB-1374
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Process flow
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
When used distributed tranasctions the transaction is rolled back when runtime exception
is thrown. Unfortunately the jBPM encapsulates RuntimeExceptions into JBPMExceptions that
are checked. Thus the rollback is not executed.
Also it needs to be checked there there is no other way in ESB that will cause
RuntimException to be changed to checked Exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira