When the server broker the connection forcefully, the client should disconnect

[joliver]

RabbitMQ can forcefully close the connection. When this happens the client doesn't correctly perform any shutdown behavior.

When the error frame is received, the length of the channels slice is 0, so nothing is ever signaled of the failure.

[jjeffery]

Thanks for the contribution. It would be nice to include a test, although I acknowledge that the test coverage for the client code is not extensive as it is.

[joliver]

In looking through the source code, I'm thinking there are a lot more places where low-level TCP connectivity problems could cause a deadlock to occur (e.g. writing to a closed channel)