I am seeing an automated build hang on the unit tests. It doesn't happen
every time or on every machine (running on RHEL5). I _believe_ it was
first introduced by the changes to SocketProxy in r758852[1] (can't
reproduce the hang before that revision).
I can only reproduce the hang when running under valgrind. From adding
in some debug logging it appears to be due to the proxy connection
failing to be notified of any connection attempt and therefore keeps
waiting to accept.
I.e. the SocketProxy thread spins in the loop starting
SocketProxy.cpp:108. The main thread is meanwhile waiting for the
connection to open in BrokerFixture.cpp:98.
Has anyone else seen this? Any ideas as to what might be the issue or
how to get more information?
--Gordon.
[1] http://svn.apache.org/viewvc?view=rev&revision=758852
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]