You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/04 21:25:51 UTC

[jira] [Commented] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

    [ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121791#comment-14121791 ] 

ASF subversion and git services commented on PROTON-610:
--------------------------------------------------------

Commit 1622536 from [~astitcher] in branch 'proton/trunk'
[ https://svn.apache.org/r1622536 ]

PROTON-610: Messenger code doesn't send heartbeat frames

> proton-c: messenger doesn't honour an advertised remote idle timeout
> --------------------------------------------------------------------
>
>                 Key: PROTON-610
>                 URL: https://issues.apache.org/jira/browse/PROTON-610
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>            Reporter: Dominic Evans
>            Assignee: Andrew Stitcher
>         Attachments: 0001-ensure-messenger-honours-remote-idle-timeout.patch
>
>
> The changes under PROTON-111 added support to the underlying proton engine for honouring a remote idle timeout (as per the AMQP 1.0 spec) and sending empty null frames on a heartbeat interval to prevent the idle timeout expiring (and hence causing the client to be disconnect), However, the Messenger API doesn't currently drive the same behaviour and so will be disconnected from any broker that has implemented such a timeout.



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