[
https://issues.apache.org/jira/browse/QPID-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated QPID-5888:
-----------------------------
Component/s: (was: C++ Client)
Python Client
Description:
At present, failover is entirely hidden 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).
was:
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).
Assignee: Alan Conway (was: Gordon Sim)
> transaction should always be aborted on failover
> ------------------------------------------------
>
> Key: QPID-5888
> URL: https://issues.apache.org/jira/browse/QPID-5888
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.29
> Reporter: Gordon Sim
> Assignee: Alan Conway
> Fix For: 0.29
>
>
> At present, failover is entirely hidden 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).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
