-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StatusCheckMessage does not use specified timeout #128
Comments
This looks great! thanks I'm going to try it :) |
Hi, I tried it with a timers.startPeriodicTimer() method to check the health every minute, the weird thing is that even when I see all consumers went down and the producer gets a timeout with every message it sends I'm not getting any error and the future always returns "Done". I'm thinking on sending a message instead of doing the status check, using ask and kill the rabbit connection if I get a timeout, hoping the supervisor will restart the connection. What I don't like is that I will be getting a lot of messages I don't need in my queue. Have you had a similar problem before? Its like the connection is alive but is useless |
I'm thinking on something like this:
|
Hi,
we use the
StatusCheckMessage
to verify if a connection to rabbitmq is established. It looks like the specified timeout is never used, so the status check never runs into the timeout. Apparently the private methodwithTimeout
is unused.This example code never fails, even if rabbitmq is not available:
Workaround: We created our own
withTimeout
function and wrapped it around the Future.Cheers :)
The text was updated successfully, but these errors were encountered: