You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/09/03 18:07:47 UTC
[jira] [Resolved] (AMQ-5953) XA Transaction 'XID:[...]' has not
been started. xaErrorCode:-4 on MessageAck
[ https://issues.apache.org/jira/browse/AMQ-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5953.
-----------------------------
Resolution: Fixed
fixed up the sync around get access to the shared xatransaction map
> XA Transaction 'XID:[...]' has not been started. xaErrorCode:-4 on MessageAck
> -----------------------------------------------------------------------------
>
> Key: AMQ-5953
> URL: https://issues.apache.org/jira/browse/AMQ-5953
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.12.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.13.0
>
>
> There is a sync issue in TransactionBroker, that can result in contention on the xatransaction map.
> The result is a get returning null for something present. So an Ack cannot resolve the corresponding transaction.
> The error - transaction not started - xaErrorCode:-4
> Either a resize or unrelated remove op could cause inconsistency and presumably allow a transient null.
> Trying to reproduce reliably in a test case is elusive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)