This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 386
server and client hang on interrupt #219
Comments
Are you using amqp v0.7.4? Or experimenting w/ the latest? |
I am using amqp 0.9. It happens with 0.8.4 as well. The issue went away after switching back to 0.7.4, so I guess you shouldn't upgrade amqp for now! |
Closed
Any news on this? The old amqp version seems to block using the heroku RabbitMQ add-on. |
Is this still happening, I am unable to reproduce, may have been fixed in a recent release. With the current work being done w/ "fat" rpm's & deb's, we can now move forward w/ upgrading the amqp gem, since they have ruby 1.9.3 bundled. |
I have not tested with the newer version since filing this issue, so I don't know if it's still happening or not. If you can't repro then it's probably fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In my tests with a single sensu-server and client on the same machine, both processes always hang when killed. The only thing that will make them exit is kill -9.
I investigated and found that the unsubscribe blocks hang indefinitely. Removing them fixes the issue but that's not a real solution.
The text was updated successfully, but these errors were encountered: