Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.29
-
None
Description
At present, if a commit is the first operation after a failover, it will be aborted. However if any other operation (e.g. a send or accept) is done after the failover, but before the commit, then the subsequent commit will succeed.
This hides the failover from the client which is the wrong thing to do for a transactional session.
The client should always abort the transaction on a failed session, and not try to failover transparently. This is what would happen if the commit failed due to some internal error on the broker (e.g. no space on disk or whatever).
Attachments
Issue Links
- is cloned by
-
QPID-5888 transaction should always be aborted on failover
- Closed