-
Notifications
You must be signed in to change notification settings - Fork 9
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
Socket probe transport doesn't accept / handle incoming connections #21
Comments
Currently the issue that we are seeing with the current setup is:
How to resolve the issue:
|
It looks like using Akka.io may complicate this process as SocketStatusTransport is not an actor and we will not be able to pass it through as an ActorRef. Using the AccpetAsync socket function and handling these request through Tasks may be an easier implementation. |
From looking at the implementation of After we have an initial bind with the socket, we would then create a temporary connection to echo the message back and close it immediately after to accept queued connections. Adding between the if statement and the exception would allow the connection request to come through and close once it has been acknowledged? |
closed via #25 |
Given how this is implemented:
akkadotnet-healthcheck/src/Akka.HealthCheck/Transports/Sockets/SocketStatusTransport.cs
Lines 35 to 37 in 85ef553
We never actually handle the incoming socket requests, thus the liveness probe will eventually fail given enough time. Need to actually handle the socket request and verify it by sending back some trivial piece of data.
Can you make this fix and verify it via a TCP integration test @izavala ?
The text was updated successfully, but these errors were encountered: