Declare DirectPublisher exchanges with passive=True
If rabbit dies, the consumer can be disconnected before the publisher
sends, and if the consumer hasn't declared the queue, the publisher's
will send a message to an exchange that's not bound to a queue, and
the message wll be lost. Setting passive=True will cause the
publisher to fail and retry if the consumer hasn't declared the
receiving queue yet.
Reviewed: https:/ /review. openstack. org/173724 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=33f3b18539d a88ddf984ada4b6 3e2767d64438f9
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit 33f3b18539da88d df984ada4b63e27 67d64438f9
Author: Mehdi Abaakouk <email address hidden>
Date: Tue Jul 22 09:42:52 2014 -0700
Declare DirectPublisher exchanges with passive=True
If rabbit dies, the consumer can be disconnected before the publisher
sends, and if the consumer hasn't declared the queue, the publisher's
will send a message to an exchange that's not bound to a queue, and
the message wll be lost. Setting passive=True will cause the
publisher to fail and retry if the consumer hasn't declared the
receiving queue yet.
Co-Authored-By: Noel Burton-Krahn <email address hidden> 65b7b642d723c05 02e7093795)
Closes-Bug: #1338732
(cherry picked from commit 434b5c8781b36cd
Conflicts: messaging/ _drivers/ common. py messaging/ tests/test_ utils.py
oslo_
oslo_
Change-Id: I5ba4d311b97236 d3a85a9f5badff6 1f12b08c12d