That seems strange. What is the error status/message received on the clients for such RPCs?
On Friday, May 10, 2019 at 4:50:39 AM UTC-7, Svante Karlsson wrote: > > I've started looking at server streaming in C++ with > greeter_async_server.cc as starting point. > I've overridden AsyncNotifyWhenDone() to capture when the client closes > the stream. All is good in the "normal" state. > > Many clients streams live data endlessly. When I kill a client either with > ctrl-c or nicely so it's exiting with "channel.reset()" the server is for > sure notified of the exiting connection going away but other unrelated > streaming rpc's (not always and not all of them) also gets closed (and > then restarted from the client) What is going on and is it possible to > prevent this unexpected stream close? > > /svante > > > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/86372bc4-11ad-430f-a6ae-72b0f5044dff%40googlegroups.com.
