Issue while publishing `cannot use a channel that was already closed!` about hutch HOT 10 CLOSED

My guess is a new channel is not opened.

from hutch.

any idea how to ensure a new channel is created?

from hutch.

@apneadiving Bunny::Session#create_channel. Please use Bunny documentation for such questions in the future.

from hutch.

I clearly see it's a Bunny exception.

But it's triggered from Hutch which is supposed to abstract it right?

Is this a bug in Hutch?

from hutch.

Hutch needs to create a new channel whenever a new connection is created. Plus see RabbitMQ logs if there are any channel-level exceptions.

from hutch.

Ok, so if its not creating a new channel, can I assume there is a bug in hutch somewhere?

from hutch.

It is most likely creating a channel, but some exception occurs that causes
rabbitmq to close the channel
On Dec 31, 2013 9:11 AM, "Benjamin Roth" [email protected] wrote:

Ok, so if its not creating a new channel, can I assume there is a bug in
hutch somewhere?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/70#issuecomment-31395862
.

from hutch.

@nelseric thanks for this useful information, I've a track to follow now.

from hutch.

It can be a bug in Hutch or just a system-specific issue that trips Hutch, e.g. an exchange is redeclared with a different set of properties.

from hutch.

There were no exceptions in rabbit logs, I ended up using the broker directly and it works fine. Thanks!

from hutch.