[
https://issues.apache.org/jira/browse/PROTON-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928606#comment-16928606
]
Alan Conway commented on PROTON-1890:
-------------------------------------
[~bajanfella] the dispatcher is suppose to pick up the error from the
TRANSPORT_CLOSED event, that's why it ignores the PN_TRANSPORT_ERROR event, as
it repeats the same information available on the CLOSED. In your logs are you
seeing a PN_TRANSPORT_CLOSED event? There should always be one, regardless how
the transport terminates.
If you can put together a small piece of code that reproduces the issue that
would help greatly.
> [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: proton-0.16.0
> Reporter: Praveen Bodke
> Assignee: Alan Conway
> Priority: Major
> Attachments: PROTON-1890.zip, examples.diff
>
>
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
