I think technically, the while (await requestStream.MoveNext()) on your server side could also throw an exception if the client stream throws an exception. But since all Tasks seems to be awaited and since you get back in the while loop, this shouldn't be the problem. My best guess is that any of the listeners.Add or listeners.Remove calls throw an exception due to concurrent access (likely remove itterates through the entries and add/remove modifies the list).
As Jan suggested, the easiest way to find out is to wrap the entire handler into a try-catch block and just look at the exception there as it's definetly caused by an undealt exception from the user code. -- 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 post to this group, send email to [email protected]. 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/d4e449b4-fca5-4c01-b8f2-eb04411b75de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
