[
https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401803#comment-16401803
]
Miha Plesko commented on PROTON-1782:
-------------------------------------
[~aconway] I confirm we're not getting "local-idle-timeout expired" error
anymore with your patch. Also looking at WireShark I can see that client is now
sending empty heartbeat messages as expected. Many thanks for this! I's running
for more than an hour in my envirnoment and everything looks great. Awesome! :)
I'm not sure what's the release policy for qpid_proton gem, but is it possible
to merge this patch upstream and release a new version of qpid_proton gem soon?
I'd really like to start using it so I kindly ask for an estimate when it's
expected to be available on Rubygems. If it's not doable in a few days, then we
will override our Container with your patch.
Thanks again for amazing response time.
> [ruby] implement idle_timeout and heartbeats
> --------------------------------------------
>
> Key: PROTON-1782
> URL: https://issues.apache.org/jira/browse/PROTON-1782
> Project: Qpid Proton
> Issue Type: Improvement
> 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 container does not wake up to service transport ticks, which means
> heartbeat frames are not sent to respect the idle_timeout settings.
> All the heartbeat and idle timeout logic is already implemented by the C
> library, the ruby Container only needs to ensure it wakes up often enough to
> service connections on time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
