-
Notifications
You must be signed in to change notification settings - Fork 20
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
Ping rabbitmq / timeout #312
Labels
enhancement
New feature or request
Comments
Yes. It makes sense, but it will be for all the RPC calls. .rpcTimeout(......) |
Thanks 😉 |
Gsantomaggio
added a commit
that referenced
this issue
Jun 7, 2024
closes: #312 Signed-off-by: Gabriele Santomaggio <[email protected]>
@plaluisalves can you please try #313? |
It is working! Thanks for the quick response and solution 😉 |
Gsantomaggio
added a commit
that referenced
this issue
Jun 10, 2024
closes: #312 Signed-off-by: Gabriele Santomaggio <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Hi Guys, not sure if here is the right channel to ask, but is it possible to have a ping method for rabbitmq stream plugin or the timeout variable could be expose?
I m start and stop the container for rabbitmq, and if the container is down, I try to connect, at first, I received an error related with a timeout, and the second time is more fast.
The first error I got is this:
2024/06/07 14:12:30 [error] - timeout 10000 ns - waiting Code, operation: commandPeerProperties
2024/06/07 14:12:30 [error] - Can't set the peer-properties. Check if the stream server is running/reachable
The seconde error is this:
dial tcp 127.0.0.1:5552: connectex: No connection could be made because the target machine actively refused it.
Describe the solution you'd like
My question is, could this timeout be expose, and we define the timeout on EnvironmentOptions, I don't want to wait 10s just to find out that the server is down?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: