[
https://issues.apache.org/jira/browse/QPID-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641048#comment-13641048
]
Andrew Stitcher commented on QPID-3828:
---------------------------------------
In fact I think this change is indeed the correct fix for this problem -
In effect it treats a heartbeat failure *as if* it was the other side of the
connection just closing the connection at their end.
The only potential problem is the connection recovering before the socket is
actually closed and this is prevented by running the disconnect operation
(which will actually call close() on the the socket ultimately) "on the
socket's thread".
> 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
> Assignee: Andrew Stitcher
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
