Mehdi Abaakouk e1ac7f8862 rabbitmq: don't wait for message ack/requeue ... I don't see any obvious reason why we should wait ack/requeue is done. This waiter have already be removed from amqp1. https://git.openstack.org/cgit/openstack/oslo.messaging/tree/oslo_messaging/_drivers/amqp1_driver/controller.py#n242 So, this change remove it from rabbitmq driver too. Closes-bug: #1734788 Change-Id: I5ecedc762596181be19410b863851a0054fd6579 (cherry picked from commit c38857e110)		2017-12-01 11:35:36 +01:00
..
add_reno-3b4ae0789e9c45b4.yaml	Add reno for releasenotes management	2016-05-19 17:14:31 +03:00
connection_ttl-2cf0fe6e1ab8c73c.yaml	Introduce TTL for idle connections	2016-07-22 13:03:04 +03:00
option-rabbitmq-max_retries-has-been-deprecated-471f66a9e6d672a2.yaml	Add deprecated relnote for max_retries rabbit configuration option	2016-07-12 17:40:01 -07:00
rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml	rabbitmq: don't wait for message ack/requeue	2017-12-01 11:35:36 +01:00