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
We are constantly getting this error "com.rabbitmq.client.AlreadyClosedException: connection is already closed due to connection error; protocol method: #method<connection.close>(reply-code=504, reply-text=CHANNEL_ERROR - second 'channel.open' seen, class-id=20, method-id=10)" with langohr 5.2.0. We are using a 5 node RabbitMQ cluster running version 3.9.11. We are opening a new channel for every publish, we close the channel immediately after the publish, to prevent race conditions. We saw the second 'channel.open' seen even on the RabbitMQ broker. This error was not present when we were using the RabbitMQ server 3.8.5 with langohr 5.2.0. After upgrading to 3.9.11 we're facing this issue.
The text was updated successfully, but these errors were encountered:
We are constantly getting this error
"com.rabbitmq.client.AlreadyClosedException: connection is already closed due to connection error; protocol method: #method<connection.close>(reply-code=504, reply-text=CHANNEL_ERROR - second 'channel.open' seen, class-id=20, method-id=10)"
with langohr5.2.0
. We are using a 5 node RabbitMQ cluster running version3.9.11
. We are opening a new channel for every publish, we close the channel immediately after the publish, to prevent race conditions. We saw thesecond 'channel.open' seen
even on the RabbitMQ broker. This error was not present when we were using the RabbitMQ server3.8.5
withlangohr 5.2.0
. After upgrading to3.9.11
we're facing this issue.The text was updated successfully, but these errors were encountered: