qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-5888) transaction should always be aborted on failover
Date Tue, 15 Jul 2014 22:13:06 GMT

     [ https://issues.apache.org/jira/browse/QPID-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alan Conway updated QPID-5888:

    Attachment: qpid-txtest2.cpp.diff

Hi Gordon,

Trying your new TX test against a plain broker, no failures. 

This passes:
time src/tests/qpid-txtest2 $OPTS --messages-per-tx=10 --tx-count=100

But this fails:
time src/tests/qpid-txtest2 $OPTS --messages-per-tx=100 --tx-count=100

Transfer tx-test2-2 to tx-test2-1 interrupted: No message to fetch
Transfer tx-test2-1 to tx-test2-2 interrupted: No message to fetch

It fails on the first transaction. I added some extra logging and error
checking to txtest, attached.

Any ideas?

> 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
>         Attachments: qpid-txtest2.cpp.diff
> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message