[rabbitmq-discuss] AlreadyClosedException always sets hardError and initiatedByApplication to true

Michael Klishin mklishin at gopivotal.com
Mon Oct 21 21:26:38 BST 2013

On 22 Oct 2013, at 00:17, Jonathan Halterman <jhalterman at gmail.com> wrote:

> After declaring a consumer on a non-existent queue several times, the connection is still in tact even though the AlreadyClosedException indicates a connection closure

Consuming from a non-existent queue should result in a channel exception
which closes the channel, not the connection.


More information about the rabbitmq-discuss mailing list