You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/07/23 13:19:31 UTC

[jira] Resolved: (QPID-805) Client does not correctly report ConnectionClose error codes to client

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

Martin Ritchie resolved QPID-805.
---------------------------------

    Resolution: Fixed

ConnectionCloseMethodHandler now calls session.notifyError if there was a non REPLY_SUCCESS error.

This will notify all waiters (Frame and State)

Then CCMH closes the Connection (session.closeProtocolSession()).

If there was no state waiter for the error the StateManager stores the error so that it can be interrogated.



> Client does not correctly report ConnectionClose error codes to client
> ----------------------------------------------------------------------
>
>                 Key: QPID-805
>                 URL: https://issues.apache.org/jira/browse/QPID-805
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2.1
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>
> Currently when a ConnectionClose Method is received the CloseOK is sent to the broker which closes the tcp connection. The client detects this and notifies the client _BEFORE_ it has processed the exception that is thrown in the ConnectionCloseMethodHandler to signal the error.

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