This repository has been archived by the owner on Sep 11, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 143
Emit more specific error than [amqp] Detected TCP connection failure
#222
Comments
This was referenced Apr 2, 2016
nhooey
added a commit
to nhooey/amqp
that referenced
this issue
Apr 2, 2016
Awesome, thanks @michaelklishin! When can you cut a new release? I'd like to get this in to Sensu as soon as possible. |
In the next few days. |
michaelklishin
pushed a commit
that referenced
this issue
Apr 4, 2016
@nhooey I've released In general, I'd highly recommend Sensu to switch to Bunny. amqp gem is not being actively maintained. |
@portertech What do you think about cutting a new release of Sensu using this version, and then switching to Bunny? |
Thanks for releasing his on short notice, @michaelklishin. |
jsonn
pushed a commit
to jsonn/pkgsrc
that referenced
this issue
Oct 17, 2016
## Changes Between 1.5.x and 1.6.0 (Apr 4th, 2016) ### amq-protocol Update Minimum `amq-protocol` version is now `2.0.1`. ### Provide More Details in TCP Connection Failure Exception Contributed by Neil Hooey. GH issue: [#222](ruby-amqp/amqp#222). ### Ensures frameset is cleared after an unhandled exception Ensures frameset is cleared after an unhandled exception. This avoids confusing exceptions such as ``` undefined method `method_class' for #<AMQ::Protocol::BodyFrame:0x0000001e8a60b0> ``` Contributed by Michael Lutsiuk. GH issue: [#218](ruby-amqp/amqp#218)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This line in
lib/amqp/session.rb
emits[amqp] Detected TCP connection failure
during the following conditions, which the comment lists:Which is a lot of conditions to summarize in the word "failure".
The error should be specific so someone has a hope of troubleshooting the connection error.
The text was updated successfully, but these errors were encountered: