activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From clebertsuconic <...@git.apache.org>
Subject [GitHub] activemq-artemis pull request: ARTEMIS-136 - XA Error fix with pro...
Date Mon, 15 Jun 2015 20:30:22 GMT
GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-artemis/pull/28

    ARTEMIS-136 - XA Error fix with proper exception error

    https://issues.apache.org/jira/browse/ARTEMIS-136
    
    From what I researched from implementers of XA TM if you throw ERR over communication
errors the transaction manager will create
    an heuristic transaction to be manually dealt with.
    
    Other XA Implementations (such as Oracle JDBC) are return FAIL over communication failures
during any XA operation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-artemis master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #28
    
----
commit f883ce925df31508d0a698aa1662cbde5820d885
Author: Clebert Suconic <clebertsuconic@apache.org>
Date:   2015-06-15T20:27:54Z

    ARTEMIS-136 - XA Error fix with proper exception error
    
    https://issues.apache.org/jira/browse/ARTEMIS-136
    
    From what I researched from implementers of XA TM if you throw ERR over communication
errors the transaction manager will create
    an heuristic transaction to be manually dealt with.
    
    Other XA Implementations (such as Oracle JDBC) are return FAIL over communication failures
during any XA operation.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message