[
https://issues.apache.org/jira/browse/QPID-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-3759.
----------------------------------
Resolution: Fixed
There are 4 commits for this from 5+ months ago so im going to assume its done,
resolving.
> Heartbeat timeout in Windows does not lead to timely reconnect
> --------------------------------------------------------------
>
> Key: QPID-3759
> URL: https://issues.apache.org/jira/browse/QPID-3759
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.14
> Environment: Windows C++ messaging
> Reporter: Chuck Rolke
> Assignee: Cliff Jansen
> Fix For: 0.17
>
> Attachments: main.cpp
>
>
> Reported by Wolf Wolfswinkel on Qpid users
> http://qpid.2158936.n2.nabble.com/Heartbeats-in-C-broker-on-Windows-td7118702.html
> 22-Dec-2011
> The simplest test case is in attached main.cpp. Establish a good network
> connection to the broker and then start the program. It creates a connection,
> sends two messages, and then pauses for 15 seconds. During the pause
> disconnect the network connection to the broker for at least two heartbeat
> timeouts (12 seconds).
> After the heartbeat timeout the timer task fires and a debug trace shows:
> Traffic timeout, TCPConnector::abort, TCPConnector::eof, TCPConnector::close
> But the connection is not actually closed until something happens on the
> network to wake up the thread waiting in Poller::run().
> The timer event appears unable to interrupt the IO thread waiting for the
> completion port.
--
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]
