You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have declared multiple direct exchanges with a same name, only different routing key then exchange->remove() will print an error in the RabbitMQ log.
The pattern would be like in http://www.rabbitmq.com/tutorials/tutorial-four-python.html
where multiple queues are binded to the same exchange. Check the "Multiple bindings" section in that tutorial.
If we do exchange->remove() when in some app that exchange is not needed anymore, it cannot actually be removed from RabbitMQ if other apps are also using the same exchange name.
Hence, even if we try to do exchange->deleteLater(), the destructor of QAMQP::Exchange will call remove() and we'll get the same behavior.
The text was updated successfully, but these errors were encountered:
@amybt I believe the behavior of calling remove in the dtor is incorrect, I've corrected this in my fork qamqp-ng. You can look at the tutorials there as well in the "tutorials" folder, tutorial 4 from the rabbitmq site is implemented there.
If we have declared multiple direct exchanges with a same name, only different routing key then exchange->remove() will print an error in the RabbitMQ log.
The pattern would be like in http://www.rabbitmq.com/tutorials/tutorial-four-python.html
where multiple queues are binded to the same exchange. Check the "Multiple bindings" section in that tutorial.
If we do exchange->remove() when in some app that exchange is not needed anymore, it cannot actually be removed from RabbitMQ if other apps are also using the same exchange name.
Hence, even if we try to do exchange->deleteLater(), the destructor of QAMQP::Exchange will call remove() and we'll get the same behavior.
The text was updated successfully, but these errors were encountered: