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 2013/12/09 21:34:07 UTC
[jira] [Resolved] (QPID-5389) ConnectionHandler may stop writting
pending frames if close is called right after the connection is started
[ https://issues.apache.org/jira/browse/QPID-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey resolved QPID-5389.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.27
Assignee: Rob Godfrey
> ConnectionHandler may stop writting pending frames if close is called right after the connection is started
> -----------------------------------------------------------------------------------------------------------
>
> Key: QPID-5389
> URL: https://issues.apache.org/jira/browse/QPID-5389
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Xin Chen
> Assignee: Rob Godfrey
> Fix For: 0.27
>
> Attachments: QPID-5389.patch
>
>
> ConnectionEndpoint._closedForOutput is set to true when close is called. Right now HeaderBytesSource.closed() returns false but _buffer has been completely consumed, which results in a deadloop in writing this 0-length buffer. Regardless of this value, the connection handler should write out all pending frames in the queue.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org