Commit 1594277 from [~gsim] in branch 'qpid/trunk'
The issue has been fully fixed, tested on RHEL 6.5 i/x on candidate packages: perl-qpid-0.22-13.el6.x86_64 perl-qpid-debuginfo-0.22-13.el6.x86_64 python-qpid-0.22-15.el6.noarch python-qpid-proton-doc-0.6-2.el6.noarch python-qpid-qmf-0.22-33.el6.x86_64 qpid-cpp-client-0.22-42.el6.x86_64 qpid-cpp-client-devel-0.22-42.el6.x86_64 qpid-cpp-client-devel-docs-0.22-42.el6.noarch qpid-cpp-client-rdma-0.22-42.el6.x86_64 qpid-cpp-debuginfo-0.22-42.el6.x86_64 qpid-cpp-server-0.22-42.el6.x86_64 qpid-cpp-server-devel-0.22-42.el6.x86_64 qpid-cpp-server-ha-0.22-42.el6.x86_64 qpid-cpp-server-linearstore-0.22-42.el6.x86_64 qpid-cpp-server-rdma-0.22-42.el6.x86_64 qpid-cpp-server-xml-0.22-42.el6.x86_64 qpid-java-client-0.22-6.el6.noarch qpid-java-common-0.22-6.el6.noarch qpid-java-example-0.22-6.el6.noarch qpid-jca-0.22-2.el6.noarch qpid-jca-xarecovery-0.22-2.el6.noarch qpid-jca-zip-0.22-2.el6.noarch qpid-proton-c-0.7-2.el6.x86_64 qpid-proton-c-devel-0.7-2.el6.x86_64 qpid-proton-c-devel-doc-0.6-2.el6.noarch qpid-proton-debuginfo-0.7-2.el6.x86_64 qpid-qmf-0.22-33.el6.x86_64 qpid-qmf-debuginfo-0.22-33.el6.x86_64 qpid-qmf-devel-0.22-33.el6.x86_64 qpid-snmpd-1.0.0-16.el6.x86_64 qpid-snmpd-debuginfo-1.0.0-16.el6.x86_64 qpid-tests-0.22-15.el6.noarch qpid-tools-0.22-13.el6.noarch rh-qpid-cpp-tests-0.22-42.el6.x86_64 ruby-qpid-0.7.946106-2.el6.x86_64 ruby-qpid-qmf-0.22-33.el6.x86_64 All symptoms are gone: * qpidd federation route not staying in Connecting|Closed by peer state now residing mainly in Waiting|Connection refused or Waiting|Closed by peer state * qpidd starts trying to reconnect forever * when modified 'server' with wait at the end qpid-route finally shows state toggling as expected (Waiting <-> Operational) -> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1296.html