In an environment where the Rabbit server configurations are managed manually and where it is important to maintain the performance KPIs, it has a negative impact when checking the existence of the queue which maintains the state of the channel in running.
This situation is not desired as it impacts the performance of the RabbitMQ server and gives information incorrect on the push status of the messages detected in the server monitoring console.
In this context we need to submit the queue existence check to a configuration parameter. At the moment we propose to activate the check only if you ask the library to create the queue.
Best regards.
Rebus is MIT-licensed. The code submitted in this pull request needs to carry the MIT license too. By leaving this text in, I hereby acknowledge that the code submitted in the pull request has the MIT license and can be merged with the Rebus codebase.
In an environment where the Rabbit server configurations are managed manually and where it is important to maintain the performance KPIs, it has a negative impact when checking the existence of the queue which maintains the state of the channel in running.
This situation is not desired as it impacts the performance of the RabbitMQ server and gives information incorrect on the push status of the messages detected in the server monitoring console.
In this context we need to submit the queue existence check to a configuration parameter. At the moment we propose to activate the check only if you ask the library to create the queue.
Best regards.
Rebus is MIT-licensed. The code submitted in this pull request needs to carry the MIT license too. By leaving this text in, I hereby acknowledge that the code submitted in the pull request has the MIT license and can be merged with the Rebus codebase.