That seems like a good idea. I think this bug is more important the other two so I'd like to be able to verify it first.
I'm now seeing the problem Petr highlighted. Feedback on updated version soon.
Test is modified and running well so far, final result in coming two days. Patch I use atm: --- cluster_test_logs.py.0 2011-03-07 10:23:00.000000000 +0100 +++ cluster_test_logs.py 2011-07-26 13:21:50.000000000 +0200 @@ -63,6 +63,7 @@ 'Running in a cluster, marking store', 'debug Sending keepalive signal to watchdog', # Watchdog timer thread 'last broker standing joined by 1 replicas, updating queue policies.', + 'error Connection timed out: closing', 'Connection .* timed out: closing' # heartbeat connection close ]) # Regex to match a UUID
The defect has been fixed, tested on RHEL 5.7 i386 / x86_64 in long stress test on packages: python-qmf-0.7.946106-14.el5 python-qpid-0.7.946106-15.el5 qmf-0.7.946106-33.el5 qmf-devel-0.7.946106-33.el5 qpid-cpp-client-0.7.946106-33.el5 qpid-cpp-client-devel-0.7.946106-33.el5 qpid-cpp-client-devel-docs-0.7.946106-33.el5 qpid-cpp-client-ssl-0.7.946106-33.el5 qpid-cpp-server-0.7.946106-33.el5 qpid-cpp-server-cluster-0.7.946106-33.el5 qpid-cpp-server-devel-0.7.946106-33.el5 qpid-cpp-server-ssl-0.7.946106-33.el5 qpid-cpp-server-store-0.7.946106-33.el5 qpid-cpp-server-xml-0.7.946106-33.el5 qpid-java-client-0.10-6.el5 qpid-java-common-0.10-6.el5 qpid-java-example-0.10-6.el5 qpid-tools-0.7.946106-12.el5 sesame-0.7.4297-6.el5 -> 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. http://rhn.redhat.com/errata/RHBA-2011-1147.html