You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2011/03/15 23:58:29 UTC
[jira] Resolved: (QPID-2994) transactions atomicity violated by
'transparent' failover
[ https://issues.apache.org/jira/browse/QPID-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-2994.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
0.10
Fixed along with related issues - QPID-3042 & QPID-3043.
Tested manually and added a test case to the test harness in testkit.py
> transactions atomicity violated by 'transparent' failover
> ---------------------------------------------------------
>
> Key: QPID-2994
> URL: https://issues.apache.org/jira/browse/QPID-2994
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6, 0.7, 0.8
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.10
>
> Attachments: QPID-2994.patch
>
>
> The messages published within a batch at the point the connection failsover appear to be replayed outside of any transaction.
> Steps to Reproduce:
> 1. start transactional session on failover enabled connection
> 2. send batches of messages in transactions
> 3. kill the cluster node the client is connected to, to trigger failover mid
> transaction
> This happens due to the lower layer replaying unacked messages upon resuming the connection.
> Message replay should not happen on a transacted session as there is no benefit of doing so.
--
This message is automatically generated by JIRA.
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:dev-subscribe@qpid.apache.org