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 current implementation is not handling channel errors well. The only expected response from these kind of calls is a corresponding OK method, like exchange.declare-ok, I guess it should also expect channel.close, and return it as an error.
Although, for this particular error it is strange that the server returns an error, because in the protocol specification it says that the server MUST ignore the auto-delete field if the exchange already exists.
Steps to reproduce:
Notice
auto_delete
changes.Panics with: AMQP Error: Unexpected method frame: channel.close, expected: exchange.declare-ok.
I'd expect
exchange_declare
to tell me that exchange is already declared without auto_delete feature.The text was updated successfully, but these errors were encountered: