[esb-issues] [JBoss JIRA] Commented: (JBESB-1438) JMS Courrier does not support transacted mode
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Mon Dec 1 10:33:36 EST 2008
[ https://jira.jboss.org/jira/browse/JBESB-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440596#action_12440596 ]
Kevin Conner commented on JBESB-1438:
-------------------------------------
To the best of our knowledge this bug no longer exists in the product. I suspect you are seeing something different but we should pursue this on the forums until we can identify what it is.
> JMS Courrier does not support transacted mode
> ---------------------------------------------
>
> Key: JBESB-1438
> URL: https://jira.jboss.org/jira/browse/JBESB-1438
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation, Examples, Process flow, Rosetta
> Affects Versions: 4.2.1
> Reporter: Jiri Pechanec
> Assignee: Mark Little
> Priority: Blocker
> Fix For: 4.2.1 CP1
>
> Attachments: trans.tgz
>
>
> JMS Courrier (deliver side) operates only with non-transacted queue sessions. This prevents jBPM integration to work correctly. The problem can be sketched this way
> 1) The message is received via JMS/JCA listener, transaction is started
> 2) jBPM process is invoked
> 3) jBPM process sends message (calls service) in non-transacted mode
> Three situations can happen
> 1) Exception is thrown later, it means that global transaction is rolled back but another service was already invoked - BUG
> 2) jBPM process goes to the wait state and waits for response from ESB, global transaction is committed, called service sends back signal to continue process - OK
> 3) jBPM process goes to the wait state and waits for response from ESB, called service sends back signal to continue process - but the global transaction was not committed yet - BUG
> This is key feature to have ESB/jBPM integration working safely.
--
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
More information about the esb-issues
mailing list