[
https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097153#comment-14097153
]
Andrew Stitcher commented on PROTON-610:
----------------------------------------
[~dnwe] If you could add a unit test (that currently fails, but succeeds after
your patch) it would save significant work in applying your patch.
The relevant tests can probably be found in
tests/python/proton_tests/messenger.py. There are also engine level idle
timeout tests to use as a reference in tests/python/proton_tests/engine.py
> 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
> 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.2#6252)
