-
Notifications
You must be signed in to change notification settings - Fork 55
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
shutdown server while client is still connected #57
Comments
I came across this too recently, I ended up adding a Something along the lines of:
which is called from a new method on ActiveRpcs:
which in turn is called from Service!
|
Hm... interesting..
so I added a |
Neither the TryCancel nor the OnServerShutdown (at least as done in #58) works. I have a working solution through custom callback via execution context, but it would be nice to have this supported by default. |
Is there a way to cleanly shutdown the server while there are still clients connected (i.e. finish the connections)?
I could not find any method/callback for this.. Am I missing something or is this not implemented?
When I try to shutdown the server and a RpcHandler is still running (because the client didn't disconnect yet), it will just hang forever.
If I then shutdown the client I get a failure with
RPCs still in flight
:-> hangs here until I shutdown the client and then fails:
It would be nice to have a
OnShutdown
callback in theRpcHandler
(where the handler could then finish the write and hence shutdown the connection to the client).Or should this be done e.g. by registering a custom callback via
ExecutionContext
?The text was updated successfully, but these errors were encountered: