You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/10/25 18:33:52 UTC
[jira] Created: (QPID-662) Transactional state is not correctly
reported after failover.
Transactional state is not correctly reported after failover.
-------------------------------------------------------------
Key: QPID-662
URL: https://issues.apache.org/jira/browse/QPID-662
Project: Qpid
Issue Type: Bug
Affects Versions: M2, M2.1
Reporter: Martin Ritchie
Assignee: Martin Ritchie
Fix For: M2.1
If a connection fails during a transaction the next commit() call may suceed but only commit the activity since failover.
So given the sequence:
send(a)
-------------------connection fails
send(b)
commit()
receive() == a
receive() == b
Message b will be committed and no error will be reported, but the first message received will be b and a will have been lost.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-662) Transactional state is not correctly
reported after failover.
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-662.
---------------------------------
Resolution: Fixed
TxnTest updated to cover additional test cases.
1) Send + Receive after failover (Auto-ACK)
2) Send , Failover , Commit (catch exception)
3) Send , Failover , Send (catch exception)
3) Send , Failover , Rollback, Send , Send (No exceptions)
> Transactional state is not correctly reported after failover.
> -------------------------------------------------------------
>
> Key: QPID-662
> URL: https://issues.apache.org/jira/browse/QPID-662
> Project: Qpid
> Issue Type: Bug
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M2.1
>
>
> If a connection fails during a transaction the next commit() call may suceed but only commit the activity since failover.
> So given the sequence:
> send(a)
> -------------------connection fails
> send(b)
> commit()
> receive() == a
> receive() == b
> Message b will be committed and no error will be reported, but the first message received will be b and a will have been lost.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.