[ 
https://issues.apache.org/jira/browse/QPID-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215117#comment-13215117
 ] 

Rob Godfrey commented on QPID-24:
---------------------------------

I've implemented the AMQP 0-10 DTX operations in the Java broker and tested 
against the existing xa tests in both Java and Python (note some of the Python 
test are still excluded because they depend on the C++ broker behaviour of 
excluded acquired messages from queue counts... if the tests are adapted to not 
depend on this behaviour the Java broker passes against them to).

Only took 5 and a half years to resolve this one... :-)
                
> Extend Qpid transaction functionality to support distributed transactions 
> (JTA)
> -------------------------------------------------------------------------------
>
>                 Key: QPID-24
>                 URL: https://issues.apache.org/jira/browse/QPID-24
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client
>            Reporter: Marnie McCormack
>            Assignee: Rob Godfrey
>             Fix For: 0.15
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Our current transaction code does not support JTA and XA. Whilst this 
> functionality is not required for JMS compliance, it is suported by 
> comparable products (ActiveMQ, SonicMQ, IBM MQ Series) and we have had 
> questions about distributed transaction support from our users.
> See section 8 of the JMS specification for details.

--
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