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)" <ji...@apache.org> on 2016/12/10 17:21:59 UTC

[jira] [Closed] (QPID-6379) Connection is stuck in close sent state on decoding errors

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

Rob Godfrey closed QPID-6379.
-----------------------------
    Resolution: Won't Fix

This client has been replaced by the new Qpid JMS client

> Connection is stuck in close sent state on decoding errors
> ----------------------------------------------------------
>
>                 Key: QPID-6379
>                 URL: https://issues.apache.org/jira/browse/QPID-6379
>             Project: Qpid
>          Issue Type: Bug
>          Components: JMS AMQP 1.0 Client
>            Reporter: Xin Chen
>
> In FrameHandler.java, the parse() method sets the state to State.ERROR on certain error conditions. Then it sends a Close frame by calling _connection.handleError().
> However, since _state is set to ERROR, all subsequent frames are ignored (by the state check in while loop). The Close frame from the peer will not be processed, so the connection is stuck in this state and there is no way for the application to recover.
> This can be easily reproduced by sending empty frames from the peer (without applying the patch in issue #29).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org