-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnhandledPromiseRejectionWarning upon deleting queue using RabbitMQ Microservice #5683
Comments
Please provide a minimum reproduction repository (as a Github/Gitlab repo) |
I've updated the Issue Description. |
Did you have a chance to have a look at it? |
I also faced this issue. Looking into a PR at the moment. It seems when a queue that we are consuming is deleted, e.g. by a troublemaker broker admin,
Since NestJS is using |
A null message is passed to callback when RabbitMQ queue is deleted. See nestjs#5683
I'm not sure if this is a expected behavior according to AMQP or RabbitMQ docs. Passing a |
Never mind, See Channel#consume
Also see amqp-node/amqplib#497 |
Bug Report
Current behavior
If the RabbitMQ microservice is connected and the queue gets deleted the error message pops up.
I found no way to catch this exception.
Input Code
Zipped Code:
nest-microservice-error.zip
Repository:
https://github.com/zvaehn/nestjs-5683-reproduction-setup
run it by:
Expected behavior
If you kill the custom_queue via lets say http://localhost:15672/#/queues the error message appears.
The application is still running though, but does not reassign the queue.
Possible Solution
I'd like to catch and react on this error.
Environment
The text was updated successfully, but these errors were encountered: