Red Hat Bugzilla – Bug 459263
AsynchIO.cpp does not handle "No route to host" error (RHEL4)
Last modified: 2008-10-06 14:59:17 EDT
+++ This bug was initially created as a clone of Bug #457913 +++
I think this is from the broker...
terminate called after throwing an instance of 'qpid::Exception'
what(): No route to host (qpid/sys/posix/AsynchIO.cpp:305)
This is from my program...
2008-aug-04 02:16:55 error Exception in client dispatch thread: Connection closed by broker
terminate called after throwing an instance of 'qpid::ConnectionException'
what(): Connection closed by broker
And this is from the broker...
+ Aborted (core dumped) ~condor/qpid.INSTALL/sbin/qpidd --no-data-dir --no-module-dir --auth no --port 15672
Seems AsynchIO.cpp is not handling all the errors it should.
--- Additional comment from email@example.com on 2008-08-05 08:29:06 EDT ---
Fixed by r682685 on trunk and r682688 on qpid.0-10
--- Additional comment from firstname.lastname@example.org on 2008-08-05 16:46:10 EDT ---
Here's another error that went to the bottom of that if ladder:
Aug 5 16:19:50 mrg2 qpidd: 2008-aug-05 16:19:50 critical Daemon startup failed: Connection timed out (qpid/sys/posix/AsynchIO.cpp:298)
Line 298 is the QPID_POSIX_CHECK(rc) line at rev 676581. I was using the 1.0 rpms.
This is reproducible by setting up a client listening on a queue on a broker, then cutting the network out and waiting, presumably, for the timeout.
Note that this problem *is* apparently addressed by the change at 682688.
--- Additional comment from email@example.com on 2008-08-05 16:56:00 EDT ---
I believe I hit this by connecting to the broker with qpid-tool over the VPN and then having the VPN disconnect (overnight). So a similar situation to what Justin encountered.
RHTS test MRG_Messaging/qpid_asynchio_fails_on_network_failure_bz457913 proves that No route to host issue is solved now (->VERIFIED)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.