consume input basicConsumeOk but response queueBindOk

[467892746]

hi,
When I used the channel. constame() method, the service returned 503 and I logged out directly, but I found that the server actually showed that the binding was successful. I forked version v1.10 and added printing, but found that it was a type mismatch. The type passed in is basicConsumeOk, but the returned type is queueBindOk. This will cause the client to exit but the server still experiences message loss due to this consumption.

I am using AWS's EKS cluster and AWS's RabbiMT version 3.13.6

[467892746]

It has been determined that it was caused by the concurrent use of the same channel to bind consumers. Can you indicate when creating a channel that concurrent consumption cannot be created.