[
https://issues.apache.org/jira/browse/QPID-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2994:
-----------------------------------
Attachment: QPID-2994.patch
The patch contains a fix for QPID-2994, QPID-3042 and QPID-3043.
1. For QPID-2994 - If a transactional session gets detached the session is now
removed and an exception is thrown.
2. For QPID-3042 - The createSession method now waits until the connection
state == OPEN before it issues a session attach.
3. QPID-3043 - A failover-lock is now used to ensure that session.create does
not proceed while the 'resume' method is in progress. However we should also
consider the possibility of the race condition where sessionCreate is called
before session resume is even started. There this fix is incomplete.
> 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: Future
>
> 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:[email protected]
