[
https://issues.apache.org/jira/browse/PROTON-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538399#comment-16538399
]
Robbie Gemmell commented on PROTON-1890:
----------------------------------------
Without more detail this report seems like it could be invalid.
{quote}
The only change i made to this example is to send messages continuously inside
the send() method.
{quote}
Depending on what you specifically mean here, this might be improper usage if
it ties up the container thread. I'd suggest you attach the diff showing what
you actually did, so someone familiar with the C++ bits (not me) might be able
to better reason about what you've done.
{quote}
The other end is detecting the error as it is sending the empty frames and no
response is heard.
{quote}
Any empty/heartbeat frames sent are entirely independent in each direction,
based on the advertised needs of the other peer. No 'response' is required or
expected.
{quote}
The proton is not sending the heartbeat messages (empty frames) as the sender
is busy in sending the data frames. Is it not necessary to send empty frames
even if the data frames are sent?
{quote}
Any empty/heartbeat frames are only sent due to the absence of other traffic.
If actual traffic is occurring, no heartbeat frames will need to be sent. As
above though, I think you could perhaps be misusing the container thread so it
cant actually do things like send heartbeats anyway.
(This all assumes the other side advertised an idle-timeout in their Open frame
to indicate they require real traffic or heartbeats at a certain frequency. If
they didn't, none will be sent as no need was indicated).
> [c++] implement idle_timeout and heartbeats
> -------------------------------------------
>
> Key: PROTON-1890
> URL: https://issues.apache.org/jira/browse/PROTON-1890
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Affects Versions: 0.16.0
> Reporter: Praveen Bodke
> Priority: Major
>
> This is similar issue reported in PROTON-1782 for ruby.
> We are facing this issue in cpp binding and i am able to reproduce the issue
> with scheduled_send_03.cpp example. The test scenario is to drop all the
> packets from both the interfaces after the successful connection. The only
> change i made to this example is to send messages continuously inside the
> send() method. The other end is detecting the error as it is sending the
> empty frames and no response is heard.
> The proton is not sending the heartbeat messages (empty frames) as the sender
> is busy in sending the data frames. Is it not necessary to send empty frames
> even if the data frames are sent?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
