You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Benjamin Graf (JIRA)" <ji...@apache.org> on 2018/07/23 16:51:00 UTC
[jira] [Updated] (ARTEMIS-1985) Produced message via OpenWire does
not get committed in XA transaction
[ https://issues.apache.org/jira/browse/ARTEMIS-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Graf updated ARTEMIS-1985:
-----------------------------------
Description:
OpenWireConnection actually does return RDONLY as result for prepare. This state causes transaction manager to ignore resource in a 2pc commit. It should be XA_OK as returned by core protocol and ActiveMQ broker.
To validate you need a XA transaction with min. 2 resources to force transaction manager to not optimize commit to 1pc.
was:
OpenWireConnection actually does return RDONLY as result for prepare. This state causes transaction manager to ignore resource in a 2pc commit. It should be XA_OK as returned by core protocol an ActiveMQ broker.
To validate you need a XA transaction with min. 2 resources to force transaction manager to not optimize commit to 1pc.
> Produced message via OpenWire does not get committed in XA transaction
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-1985
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1985
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.6.2
> Reporter: Benjamin Graf
> Priority: Critical
> Fix For: 2.7.0, 2.6.3
>
>
> OpenWireConnection actually does return RDONLY as result for prepare. This state causes transaction manager to ignore resource in a 2pc commit. It should be XA_OK as returned by core protocol and ActiveMQ broker.
> To validate you need a XA transaction with min. 2 resources to force transaction manager to not optimize commit to 1pc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)