[ 
https://issues.apache.org/jira/browse/QPID-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajith Attapattu resolved QPID-3625.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.14)
                   0.15

This change was tested by Weston in an app server environment.
                
> XASessionImpl Incorrectly sets Session acknowledge mode to AUTO_ACKNOWLEDGE 
> when it should be CLIENT_ACKNOWLEDGE
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3625
>                 URL: https://issues.apache.org/jira/browse/QPID-3625
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.10, 0.12
>         Environment: All platforms
>            Reporter: Weston M. Price
>            Priority: Critical
>             Fix For: 0.15
>
>         Attachments: QPID-3625.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using distributed transactions (XA) message acknowledgement needs to 
> occur prior to the XA transaction being started in order to consistently 
> support the two phase commit protocol. In order for this to correctly occur, 
> the XASessionImpl, a non-transacted Session (i.e. non JMS transacted session) 
> should be configured to use CLIENT_ACKNOWLEDGE as this is the only mode that 
> supports explicit message acknowledgement which again, is required to 
> correctly participate in the distributed transaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to