[
https://issues.apache.org/jira/browse/PROTON-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400309#comment-16400309
]
Alan Conway commented on PROTON-1793:
-------------------------------------
Here's what's happening: the proton-c engine will generate heartbeat events
correctly *if* it is woken up often enough. The bug in the ruby binding is that
it is not waking up the engine as needed so that it can generate them. For some
reason, requesting heartbeats is causing the engine to get woken up - which
allows it to send heartbeats as well.
Since there's no explicit code in the ruby binding to wake it up for
heartbeats, I need to review what's happening here as part of the fix, to make
sure we're not generating needless wake-ups. What client are you using in your
test above?
> [ruby] not sending heartbeat frames to respect idle-timeout
> -----------------------------------------------------------
>
> Key: PROTON-1793
> URL: https://issues.apache.org/jira/browse/PROTON-1793
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
> Affects Versions: proton-c-0.21.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Major
> Fix For: proton-c-0.22.0
>
>
> The ruby library does not send heartbeat frames when the remote end of a
> connection requests an idle-timeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
