[
https://issues.apache.org/jira/browse/QPID-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992086#comment-12992086
]
Rajith Attapattu commented on QPID-2994:
----------------------------------------
We do throw an exception indicating that failover has happened and the session
is closed.
However I think we need to explicitly mention that the transaction is
rollbacked.
We also need to document,
1. Which exceptions will destroy a session
2. And which exceptions can be handled and continue with the session.
> 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]
