The current version of the FailoverExchangeMethod is extended from the FailoverRoundRobinServer class and is subjected to limits imposed by this class for retries and cycle counts. The FailoverExchangeMethod should keep trying as long as a) The broker list update via the Failover exchange is not empty AND b) We haven't tried all entries with out sucess (total cluster failure)
This is tracked in upstream via QPID-1713 A fix for this is committed in Qpid trunk at rev 750205
Frantisek, does this issue have coverage?
VERIFIED on RHEL 5.6 / 6.2 (i686/x86_64) # rpm -qa | grep qpid | sort -u python-qpid-0.10-1.el5 python-qpid-qmf-0.10-10.el5 qpidc-debuginfo-0.5.752581-3.el5 qpid-cpp-client-0.10-8.el5 qpid-cpp-client-devel-0.10-8.el5 qpid-cpp-client-devel-docs-0.10-8.el5 qpid-cpp-client-ssl-0.10-8.el5 qpid-cpp-server-0.10-8.el5 qpid-cpp-server-cluster-0.10-8.el5 qpid-cpp-server-devel-0.10-8.el5 qpid-cpp-server-ssl-0.10-8.el5 qpid-cpp-server-store-0.10-8.el5 qpid-cpp-server-xml-0.10-8.el5 qpid-java-client-0.10-6.el5 qpid-java-common-0.10-6.el5 qpid-java-example-0.10-6.el5 qpid-qmf-0.10-10.el5 qpid-qmf-devel-0.10-10.el5 qpid-tools-0.10-6.el5 --> VERIFIED
The issue was retested and verified, clearing the NEEDINFO flag.