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)" <qp...@incubator.apache.org> on 2007/11/21 21:40:42 UTC

[jira] Created: (QPID-688) c++ client: decoding exceptions during connection setup hang the client.

c++ client: decoding exceptions during connection setup hang the client.
------------------------------------------------------------------------

                 Key: QPID-688
                 URL: https://issues.apache.org/jira/browse/QPID-688
             Project: Qpid
          Issue Type: Bug
          Components: C++ Client
            Reporter: Alan Conway
            Priority: Critical


An exception from frame.decode in client::Connector::readbuff (e.g. a decoding error) kills the network thread but does not raise an exception in the user thread, which is left hanging in client::ConnectionHandler::waitForOpen.

An exception in the connector should close the associated Connection with error & status, which will wake up any waiting user threads.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (QPID-688) c++ client: decoding exceptions during connection setup hang the client.

Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.

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

Alan Conway resolved QPID-688.
------------------------------

    Resolution: Fixed

> c++ client: decoding exceptions during connection setup hang the client.
> ------------------------------------------------------------------------
>
>                 Key: QPID-688
>                 URL: https://issues.apache.org/jira/browse/QPID-688
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client
>            Reporter: Alan Conway
>            Priority: Critical
>
> An exception from frame.decode in client::Connector::readbuff (e.g. a decoding error) kills the network thread but does not raise an exception in the user thread, which is left hanging in client::ConnectionHandler::waitForOpen.
> An exception in the connector should close the associated Connection with error & status, which will wake up any waiting user threads.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.