Description of problem: When creating a federated route (bridge) to another broker, if the bridge's AMQP session encounters an error (such as a queue reaching its maximum capacity upon delivery), messages stop flowing. Version-Release number of selected component (if applicable): 1.3 How reproducible: 100% Steps to Reproduce: 1. Set up federation between 2 brokers 2. Set up a queue in the destination broker to which federated messages will be delivered, and give it a small max message count 3. Send more messages over the bridge than the queue can hold Actual results: the bridge stops pulling messages from the source broker Expected results: the bridge should attempt to rebuild itself periodically if its underlying session has errors Additional info: this could possibly be mitigated by using producer flow control in MRG-M 2.0
Created attachment 512435 [details] Suggested patch
See https://issues.apache.org/jira/browse/QPID-3352 for details and proposed patch
Fixed upstream in revision 1145706.
Tested on RHEL6.4 (both i386 and x86_64). This issue has been fixed. Packages used for testing: python-qpid-0.22-4.el6 python-qpid-qmf-0.22-8.el6 qpid-cpp-client-0.22-10.el6 qpid-cpp-client-devel-0.22-10.el6 qpid-cpp-client-devel-docs-0.22-10.el6 qpid-cpp-client-rdma-0.22-10.el6 qpid-cpp-client-ssl-0.22-10.el6 qpid-cpp-server-0.22-10.el6 qpid-cpp-server-devel-0.22-10.el6 qpid-cpp-server-ha-0.22-10.el6 qpid-cpp-server-rdma-0.22-10.el6 qpid-cpp-server-ssl-0.22-10.el6 qpid-cpp-server-store-0.22-10.el6 qpid-cpp-server-xml-0.22-10.el6 qpid-proton-c-0.4-2.2.el6 qpid-qmf-0.22-8.el6 qpid-qmf-devel-0.22-8.el6 qpid-tools-0.22-3.el6 -> 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