-
Notifications
You must be signed in to change notification settings - Fork 124
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
** (stop) :unexpected_delivery_and_no_default_consumer #46
Comments
I have asked on the rabbitmq-users list and got the following answer: I'm not sure my implementation is correct and I couldn't create a simple example program to reproduce this error (I'm getting that error intermittently in my phoenix application). My latest try was to downgrade esl-elrlang to 19.3.6 and rabbitmq-server to 3.6.10, but I'm not convinced the problem won't happen again. |
Thanks @aeliton for sharing. Seeing number of 👍 , there are quite few people suffering the issue. I haven't managed to reproduce the issue. Any helps and information are welcome. |
Is it possible to get more detailed logs? For example... def publish do
{:ok, connection} = AMQP.Connection.open
{:ok, channel} = AMQP.Channel.open(connection)
publish(channel, "hello")
...
end
def publish(channel, queue)
AMQP.Queue.declare(channel, queue)
AMQP.Basic.publish(channel, "", queue, "Hello World!")
catch
:exit, reason ->
Logger.error "EXIT signal with #{reason} - fail to publish a message to #{queue}"
status = AMQP.Queue.status(channel, queue) # < it fails if the queue doesn't exist.
Logger.error "Queue status: #{inspect status}"
exit(:rabbit_mq_error)
end |
We had this happening during shutdown, if our terminate/2 didn't run and the channel never closed on time. Here's some related data: jcabotc/hare#8 (comment) |
I've ran into this issue when using RabbitMQ as an MQTT broker and using an incorrect password. The client would connect successfully, but when attempting to subscribe to an MQTT topic, I would get the following error on the server:
|
There is a high chance the issue is fixed on 1.2.0-rc.0 so please give it a try. I changed the way the broker process monitors other process. I believe this is caused when the client pid is shut down before channel is closed. |
If you can make sure always closing a channel before the owner process gets down, that might help too. We will release 1.2 shortly so please give it try. If neither solution - upgrading 1.2 or closing a channel - work, feel free to reopen the issue. |
We're seeing something which I think is related. Our consumers essentially shut down on rescue/catch:
And we end up with "ghost" channels that have un-acked messages on the rabbitmq side. The simplest way to reproduce this issue reliably: 1 - Run the Consumer from this project's readme (the one that sets up
3 - Send a message to the queue This is obviously extreme, but it's meant to show what happens when the I would think that closing the channel would solve this issue, but it doesn't appear to. This very rarely happens, so I'm thinking it's some timing between the message being received, the :DOWN being received and the Channel close being processed on the RabbitMQ side. |
Hi mates,
I am having a strange behavior running my consumer, once it is started by the main app supervisor, I see the following errors:
It only happens on my Rabbit QA instance, locally it goes well,
The consumer do receives messages normally 🤔
Any thoughts?
The text was updated successfully, but these errors were encountered: