Description of problem: Version-Release number of selected component (if applicable): How reproducible: easy Steps to Reproduce: 1. while make check-long LONG_TESTS=run_long_cluster_tests; do true; done Actual results: Eventually halts with an error Expected results: No error Additional info: Based on the logs it appears that a new broker was joining the cluster when an error caused the updater to retract its update. The new broker exits with an error "update connection closed prematurely"
Fixed on trunk r949767 and ported to mrg_1.3.x branch: http://mrg1.lab.bos.redhat.com/git/?p=qpid.git;a=commitdiff;h=ad3a7e4927edc01a262a0ee3903f55592b41d337
Reproduction scenario: Run indefinite loop with the test on both RHEL5 (i386, x86_64) machines. Tested with (version): qpid-cpp-client-devel-docs-0.7.946106-17.el5 qpid-cpp-mrg-debuginfo-0.7.946106-17.el5 qpid-cpp-server-0.7.946106-17.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.6-55 qpid-cpp-server-cluster-0.7.946106-17.el5 qpid-cpp-server-store-0.7.946106-17.el5 qpid-java-client-0.7.946106-10.el5 python-qpid-0.7.946106-14.el5 qpid-tools-0.7.946106-11.el5 qpid-cpp-server-xml-0.7.946106-17.el5 qpid-cpp-client-0.7.946106-17.el5 qpid-cpp-client-ssl-0.7.946106-17.el5 qpid-cpp-server-ssl-0.7.946106-17.el5 qpid-cpp-server-devel-0.7.946106-17.el5 qpid-cpp-client-devel-0.7.946106-17.el5 qpid-java-common-0.7.946106-10.el5 Tested on: RHEL5 i386,x86_64 - passed >>> VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: Bug in code handling cluster update. C: Broker joining a cluster at the same time that the cluster is handling an error failed with "update connection closed prematurely" F: Fixed the update code. R: Brokers can join a cluster successfully even when the cluster is handling an error.
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/RHSA-2010-0773.html