[
https://issues.apache.org/jira/browse/PROTON-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545633#comment-16545633
]
Praveen Bodke commented on PROTON-1890:
---------------------------------------
Thanks for the update Alan.
I have tested the same reproducer in 0.24 version and i see that the issue is
fixed.
>From the Frame logs its visible that after the close frame is sent, the proton
>immediately sending the EOS frame to close the socket.
Following are the frame log snippets.
[0x98780f0]:0 -> (EMPTY FRAME)
push-while-in
push-while-in
[0x98780f0]:0 -> (EMPTY FRAME)
push-while-in
push-while-in
push-while-in
[0x98780f0]:0 -> (EMPTY FRAME)
push-while-in
push-while-in
[0x98780f0]:0 -> (EMPTY FRAME)
push-while-in
push-while-in
push-while-in
[0x98780f0]:0 -> @close(24) [error=@error(29)
[condition=:"amqp:resource-limit-exceeded", description="local-idle-timeout
expired"]]
[0x98780f0]: -> EOS
amqp:resource-limit-exceeded: local-idle-timeout expired
Is there a way to enable proton logs from the CPP code instead of using the
PN_TRACE_FRM environment variable. My application is running under daemon and
will not have the console to display the logs.
> [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
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
