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

["Andrew Stitcher (JIRA)" <ji...@apache.org>]

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

Andrew Stitcher resolved PROTON-610.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.8

Thanks [~dnwe] for this fix -
I've applied most of this patch except for the transport logging changes. Instead of those, I fixed the frame trace logic to actually print "(EMPTY FRAME)" when sending a heartbeat frame.

> 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
>             Fix For: 0.8
>
>         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)