You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2017/11/22 12:09:00 UTC

[jira] [Closed] (QPID-7883) Python client should not raise exception on close() after stop.

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

Robbie Gemmell closed QPID-7883.
--------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: qpid-python-1.37.0)

Closing as a duplicate of QPID-7884, which is the same but has changes against it already.

> Python client should not raise exception on close() after stop.
> ---------------------------------------------------------------
>
>                 Key: QPID-7883
>                 URL: https://issues.apache.org/jira/browse/QPID-7883
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Client
>    Affects Versions: qpid-python-1.36.0
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>
> The python client throws exceptions out of AMQP object methods (Connection, Session and Link objects) if the selector has been stopped, to prevent hanging (see QPID-7317 Deadlock on publish)
> However to be robust to shut-down order, the close() method should *not* throw an exception in this case, but should be a no-op.



--
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