[
https://issues.apache.org/jira/browse/QPID-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206160#comment-13206160
]
Gordon Sim commented on QPID-3828:
----------------------------------
When the idle timeout fires., the callback request works as expected and we
call AsyncIO::queueWriteClose(). However at that point if the socket is not
writable (i.e. buffers are full), then we never get the AsyncIO::writable()
callback again (at least until the netwrok connection is re-established) and
that is where the actual close is handled.
> When sending large messages loss of connection is not detected even with
> heartbeats enabled
> -------------------------------------------------------------------------------------------
>
> Key: QPID-3828
> URL: https://issues.apache.org/jira/browse/QPID-3828
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.14, 0.15
> Reporter: Gordon Sim
>
> E.g run qpid-send --broker <remote-broker> --connection-options {heartbeat:8}
> --messages 0 --content-size 1600 --report-every 1000 --address amq.topic
> then after some time pull the network cable (you have to do this, a kill
> -STOP on the broker is *not* sufficient). The test will continue sending
> messages then eventually hang (when buffers are full). If you reconnect the
> cable, the connection will fail but if you don't, it will not.
> If you reduce the size e.g. to 100 bytes , the connection fails as expected
> after two heartbeat intervals (16 secs in this case).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
