If that is not the case, it is a bug. Could you file an issue at https://github.com/grpc/grpc-java/issues along with a reproduce-able case?
On Thursday, December 15, 2016 at 4:47:01 PM UTC-8, Eugene Strulyov wrote: > > If an exception is thrown in a StreamObserver, it will be caught in the >> JumpToApplicationThreadServerStreamListener and cause the stream to be >> closed. Eventually the exception will propagate back back to the >> serializing executor contained in the Server, which will log the exception. >> >> > > That is not the behaviour I observed. Uncaught exception in onNext() went > nowhere and was not logged (using grpc version 1.0.1). > > >> Server side deadlines are set before the ServerInterceptors are added. >> These are normally derived from the deadline provided by the client. You >> can add your own ServerInterceptor to add a deadline if you would like, >> though. >> > > If the client does not specify a deadline, is there no deadline at all? > Can you point me to an example to set up a default deadline on the server? > > thanks, > > Eugene > > -- 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/293ccba4-15f9-489f-998a-c12b20cd65bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
