Hi,I have implemented a Go gRPC server for an app backend and see that client connections and the corresponding goroutines are still running even if clients (Android apps) have died. I'm not using methods that stream results from server to client or otherwise.Is this the expected behaviour?And if so, is there some kind of way on the Go server code to iterate over client connections and then identify the old idle ones and close them?Thanks!
So if I understand correctly tcp user timeout applies to sent data that has not been acknowledged. So in this case maybe it would not apply because the server doesn't send any data to the dead client, am I right?
--Angel.
--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAFnDmdrwL6tnvPHojQfBt%2BXPiwnbNEHPXXgOcWapzvMsU14FEw%40mail.gmail.com.