[jira] Commented: (SM-1752) No rollback for failed InOnly exchange in JMS consumer endpoint

["Ron Gavlin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48415#action_48415 ] 

Ron Gavlin commented on SM-1752:
--------------------------------

Hi Gert,

How should RobustInOnly exchanges sent by a JMS consumer endpoint behave under identical circumstances? I would think ERRORs should also trigger a txn rollback in this case as well, right? If so, that doesn't appear to be the current behavior? 

What about transacted InOut exchanges sent by the JMS consumer endpoint?

Should the value of the "stateless" boolean flag determine how any transacted exchange that ends in ERROR behaves? When stateless=true, I would expect the transaction to be rolled back for all MEPs that end in ERROR. OTOH, when stateless=false, I would expect the transaction to be committed and the ERROR to be returned to the caller via JMS. Does that make sense?

What do you think?

/Ron

> No rollback for failed InOnly exchange in JMS consumer endpoint
> ---------------------------------------------------------------
>
>                 Key: SM-1752
>                 URL: https://issues.apache.org/activemq/browse/SM-1752
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: servicemix-jms-2008.01, 3.2.3
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: servicemix-jms-2008.02, 3.2.4
>
>
> If the InOnly exchange sent by a JMS consumer endpoint ends in ERROR, the transaction (jms or XA) is not being rolled back.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.