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
[RabbitMQ Trigger] Not close connection at "Stop Listening" #9159
Comments
Hey @jmtt89, Thanks for the report, I have managed to reproduce this and have created |
Hi @Joffcom , how are you? Could you tell me if this issue is related to the fact that RabbitMQ Trigger no longer fetches items from the queue with the execute button? When in production, it works normally. But when pressing the execute button to test, the rabbit trigger node stays in an infinite loop and does not continue the workflow. I have noticed this from version 0.36 onwards. |
Hi, I think it is because every time you click "test" you open a new connection, in Rabbitmq the messages are not delivered repeatedly to all conections, they are only delivered to one of them (not necessary the last created) |
Thank you very much, so I believe it is related. |
Yeah it could be related, the node really needs some updating. |
Bug Description
On Rabbit Management UI i see creating a new connection every time i click the "Test Step" and it does not close when click "Stop Listening"
To Reproduce
Expected behavior
close connection with rabbit every time i stop listening.
Operating System
Kubernetes
n8n Version
image docker.n8n.io/n8nio/n8n
Node.js Version
image docker.n8n.io/n8nio/n8n
Database
PostgreSQL
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: