You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2017/06/30 18:24:00 UTC

[jira] [Updated] (QPID-7847) qmf.client.BrokerAgent does not provide reconnect support

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

Alan Conway updated QPID-7847:
------------------------------
    Description: 
Moved from PROTON-1511 

The BrokerAgent is provided by this diff:  https://reviews.apache.org/r/52280/diff/3#0  Here is how to reproduce:

1. Instantiate a BrokerAgent connecting to a qpidd broker
2. Do something with the connected BrokerAgent object to show that it's working
3. kill qpidd with `pkill -9 -f qpidd`
4. start qpidd up again
5. Try to do step 2 again
6. Receive a traceback indicating the BrokerAgent is disconnected

My code handles reconnect support for the connection, but it's not prepared to also handle reconnect support for the BrokerAgent connection. I would like that connection to have a reconnect support option added so I can call it like:

BrokerAgent(**existing_options, reconnect=True)

Having reconnect default to True is also fine w/ me. I think users may still want the option to set it also.

  was:
[Moved from PROTON-1511]

The BrokerAgent is provided by this diff:  https://reviews.apache.org/r/52280/diff/3#0  Here is how to reproduce:

1. Instantiate a BrokerAgent connecting to a qpidd broker
2. Do something with the connected BrokerAgent object to show that it's working
3. kill qpidd with `pkill -9 -f qpidd`
4. start qpidd up again
5. Try to do step 2 again
6. Receive a traceback indicating the BrokerAgent is disconnected

My code handles reconnect support for the connection, but it's not prepared to also handle reconnect support for the BrokerAgent connection. I would like that connection to have a reconnect support option added so I can call it like:

BrokerAgent(**existing_options, reconnect=True)

Having reconnect default to True is also fine w/ me. I think users may still want the option to set it also.


> qmf.client.BrokerAgent does not provide reconnect support
> ---------------------------------------------------------
>
>                 Key: QPID-7847
>                 URL: https://issues.apache.org/jira/browse/QPID-7847
>             Project: Qpid
>          Issue Type: Bug
>          Components: QMF
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>
> Moved from PROTON-1511 
> The BrokerAgent is provided by this diff:  https://reviews.apache.org/r/52280/diff/3#0  Here is how to reproduce:
> 1. Instantiate a BrokerAgent connecting to a qpidd broker
> 2. Do something with the connected BrokerAgent object to show that it's working
> 3. kill qpidd with `pkill -9 -f qpidd`
> 4. start qpidd up again
> 5. Try to do step 2 again
> 6. Receive a traceback indicating the BrokerAgent is disconnected
> My code handles reconnect support for the connection, but it's not prepared to also handle reconnect support for the BrokerAgent connection. I would like that connection to have a reconnect support option added so I can call it like:
> BrokerAgent(**existing_options, reconnect=True)
> Having reconnect default to True is also fine w/ me. I think users may still want the option to set it also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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