You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/12/12 14:08:43 UTC

[jira] Resolved: (QPID-463) Java client doesn't close connection gracefully when faced with broker with unsuported protocol version

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

Rob Godfrey resolved QPID-463.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: M3)
                   M2.1

> Java client doesn't close connection gracefully when faced with broker with unsuported protocol version
> -------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-463
>                 URL: https://issues.apache.org/jira/browse/QPID-463
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M2
>            Reporter: Tomas Restrepo
>            Priority: Minor
>             Fix For: M2.1
>
>
> The java client currently doesn't gracefully handle the case when it finds the broker uses an unsupported protocol version, when trying to open a new connection. 
> What currently happens is that the Java client never responds with a connection.start-ok (suggesting it believes it doesn't support the specified protocol version), but neither does it actually close the TCP connection to the broker. Instead, the client retries the connection after a while, fails again to respond or close the connection, and eventually fails the connection after the connection timeout expires. 
> No error is raised to the application opening the connection at any point indicating the cause of the connection failure is a protocol mismatch.

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