[
https://issues.apache.org/jira/browse/QPID-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-142:
--------------------------------
Component/s: (was: Dot Net Client)
Removing .net client from components, as this related to the old 0-8 / 0-10
.Net clients which were removed from the repository months ago, and not the
current .Net bindings for the C++ messaging API.
> Transactions not atomic in the face of fail over
> ------------------------------------------------
>
> Key: QPID-142
> URL: https://issues.apache.org/jira/browse/QPID-142
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M3
> Reporter: Steven Shaw
>
> When some messages are already published in a transaction when fail over
> occurs, those messages will be lost.
> Options seem to be:
> 1. Remembering and replaying sent messages (in a Tx)
> 2. Aborting any in-flight transactions on failover
> 1 could be costly in terms of memory for applications using transaction. 2
> could be annoying for applications requiring the use of retry loops (however
> these retry loops are often necessary in any case and can sometimes be
> injected via AOP).
> I asked Gordon's opinion and he favored (2) as well.
> In addition to this we need to ensure that the broker issues a Channel.Close
> when it gets a Tx.Commit without a prior Tx.Select. It's not clear what error
> code should be used. Invalid-command (503) looks close but is a hard-error.
> Check the amqp-dev list for discussion on this topic.
--
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]
