-
Notifications
You must be signed in to change notification settings - Fork 145
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
504 channel/connection is not open error occurred in multiple connection with same rabbitmq service #97
Comments
Please follow the Best Practices for reporting RabbitMQ issues Please add a way to reproduce the issue: for example, a gist or github repo. Thank you |
ok, next week i will give you details |
I created a github repo to declare details, please refer to https://github.com/shinyxhh/rabbitMQProblem. Thanks. |
Thank you, we will try to find time within the next two weeks to investigate. |
@shinyxhh thanks for the details, but without code we can compile and run to observe the issue there is little chance we will be able to help. I'm looking through the log files now. |
@shinyxhh the archive you provided does NOT include RabbitMQ logs, probably because you are running RabbitMQ in docker. The logs are collected via docker, so to get them you must run this command:
...then attach |
@lukebakken I have add logs in my repo. I restarted the rabbitMq service and reproduced the error. It happened in a few minutes and three in four channels will be broken in the end which can not be recreated. |
You are trying to bind to a queue that doesn't exist:
We can't assist you unless you provide code that we can run to reproduce this situation. I will close this issue for now. If you are able to provide code, please do so, add a comment here, and I will re-open this issue. |
@lukebakken I declare a queue before I bind it, it should work even if this queue didn't exist. What reason may cause this situation. |
I make sure that there is no concurrent goroutine using shared channel.
The text was updated successfully, but these errors were encountered: