[jira] [Resolved] (PROTON-25) Connection doesn't transistion to PN_REMOTE_CLOSED when socket is closed.

["Ted Ross (JIRA)" <ji...@apache.org>]

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

Ted Ross resolved PROTON-25.
----------------------------

       Resolution: Not A Problem
    Fix Version/s: 0.1

This is not a bug, only a user error.  When the socket is closed without AMQP-level close, the connector is closed but the connection remains open.  This is a case that needs to be handled by the application.

Please note that the application may need to do some special recovery if a connector is closed and there are unsettled deliveries.
                
> Connection doesn't transistion to PN_REMOTE_CLOSED when socket is closed.
> -------------------------------------------------------------------------
>
>                 Key: PROTON-25
>                 URL: https://issues.apache.org/jira/browse/PROTON-25
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: Ted Ross
>            Assignee: Ken Giusti
>            Priority: Blocker
>             Fix For: 0.1
>
>
> After a connection has been established and opened both remotely and locally, if that connection is closed uncleanly (i.e. the socket is closed without any handshake), the connection object will not transition to PN_REMOTE_CLOSED.
> The closed connection is awakened and processed by the driver, but its state is not changed.  Any state the application has associated with the connection, its sessions, and its links will not be cleaned up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira