You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unexpected_delivery_and_no_default_consumer is expected, I think, but the "second 'channel.open' seen" is not. This causes the connection to close, which breaks all other channels using that connection.
The text was updated successfully, but these errors were encountered:
corben2
changed the title
second 'channel.open' seen error when recovoring from consumer crash
"second 'channel.open' seen" error when recovoring from consumer crash
Jul 30, 2024
corben2
changed the title
"second 'channel.open' seen" error when recovoring from consumer crash
"second 'channel.open' seen" error when recovering from consumer crash
Jul 30, 2024
the channel process is gone but it is still valid on the server side
when amqp tries to open a new channel for the queue, the server returns the "second 'channel.open' seen" error because it thinks there is another channel opened
then connection error and amqp_client (erlang lib) fails
Can you open other connections for the other queues then it won't affect other open channels?
We've worked around this by wrapping all of our message consumption in a try-catch. Otherwise, even if the consumer came back properly, I think it would just repeatedly crash on the same message.
The queue is not exclusive.
I believe I originally tried opening other connections (to the same server, however) for the other channels, and it still had the same behavior. I can retry that and get back to you, but like I said above - even if this is fixed - I think there might still be other issues, so maybe we can just close this issue.
When a consumer is actively consuming messages, crashes, and then restarts, the following errors seem to occur:
The unexpected_delivery_and_no_default_consumer is expected, I think, but the "second 'channel.open' seen" is not. This causes the connection to close, which breaks all other channels using that connection.
The text was updated successfully, but these errors were encountered: