3f4ce9470b
Consumer declaration consist of the next steps: 1) declare an exchange 2) declare a queue 3) bind the queue to the exchange Due to reply exchanges are auto-delete, at the step 3 the exchange can be removed and consumer.declare() will raise `queue.bind 404 Exchange not found`. So, in this case the queue is exist and AMQPListener just call consumer.consume() on the queue and go to drain_events() despite on the fact that the queue is unbound. This change tries to redeclare queue/exchange proactively each times channel change and just before consuming messages. Co-Authored-By: Mehdi Abaakouk <sileht@redhat.com> Closes-Bug: #1609766 Change-Id: Id8b48df3d26675d72955d417ce7622b1e8aa6195
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: http://docs.openstack.org/developer/oslo.messaging
- Source: http://git.openstack.org/cgit/openstack/oslo.messaging
- Bugs: http://bugs.launchpad.net/oslo.messaging