[
https://issues.apache.org/jira/browse/PROTON-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399180#comment-16399180
]
Jiri Daněk commented on PROTON-1793:
------------------------------------
Strangely, if you request heartbeats from your peer, and the period is less
than what the peer requested from us, the heartbeats start going in both
directions. This could be a workaround,
{noformat}
$ PN_TRACE_FRM=1 cli-proton-ruby-receiver -c 0 --log-msgs dict --broker
amqp://127.0.0.1:5672/lala --conn-heartbeat 10
[0x1fab9f0]: -> SASL
[0x1fab9f0]: <- SASL
[0x1fab9f0]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:PLAIN, :ANONYMOUS]]
[0x1fab9f0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
initial-response=b"anonymous@nixos"]
[0x1fab9f0]:0 <- @sasl-outcome(68) [code=0]
[0x1fab9f0]: <- AMQP
[0x1fab9f0]: -> AMQP
[0x1fab9f0]:0 -> @open(16)
[container-id="7b5d5572-8f69-43d8-a3af-a5168a3a31bd", channel-max=32767,
idle-time-out=5000]
[0x1fab9f0]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
outgoing-window=2147483647]
[0x1fab9f0]:0 -> @attach(18) [name="7b5d5572-8f69-43d8-a3af-a5168a3a31bd/1",
handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
[address="lala", durable=0, timeout=0, dynamic=false], target=@target(41)
[durable=0, timeout=0, dynamic=false], initial-delivery-count=0,
max-message-size=0]
[0x1fab9f0]:0 <- @open(16) [container-id="amq", max-frame-size=4294967295,
channel-max=65535, idle-time-out=30000,
offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container",
:"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS-RELAY"],
properties={:product="apache-activemq-artemis",
:version="2.4.0.amq-710004-redhat-1"}]
[0x1fab9f0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=1,
incoming-window=2147483647, outgoing-window=2147483647, handle-max=65535]
[0x1fab9f0]:0 <- @attach(18) [name="7b5d5572-8f69-43d8-a3af-a5168a3a31bd/1",
handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
[address="lala"], target=@target(41) [], incomplete-unsettled=false,
initial-delivery-count=0]
[0x1fab9f0]:0 -> @flow(19) [next-incoming-id=1, incoming-window=2147483647,
next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0,
link-credit=10, drain=false]
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 -> (EMPTY FRAME) <- HERE
[0x1fab9f0]:0 <- (EMPTY FRAME)
[0x1fab9f0]:0 <- (EMPTY FRAME)
[...]
{noformat}
> [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]
