io.grpc.SerializingExecutor swallows RuntimeExceptions thrown by gRPC services

Users can call ServerBuilder#executor() to arrange for gRPC service callbacks like onNext(), onError() and onCancelHandler to be dispatched on a custom Executor. However, when one of those callbacks throws a RuntimeException (due to bug / programming error in the service) that Executor and/or its Thread's UncaughtExceptionHandler never sees it. Instead, io.grpc.SerializingExecutor catches the RuntimeException, logs it and just keeps going.

This might be enough in the datacenter where server logs are typically retained for later debugging, but for mobile "on-device" gRPC servers, the java.util.logging output isn't typically seen by anyone. In that environment, it's more common to handle unexpected Exceptions programmatically and gRPC should somehow make this possible.

Comienza con io.grpc.SerializingExecutor y la ruta ServerBuilder#executor() descrita en el issue. Rastrea cómo se gestionan las RuntimeExceptions de callbacks del servicio como onNext(), onError() y onCancelHandler, y determina después un comportamiento explícito que permita a los servidores móviles gestionarlas mediante programación en lugar de limitarse a registrarlas. Se considera terminado cuando el comportamiento de manejo de excepciones elegido está definido y verificado.

Escrito por el modelo de indexación a partir del texto del issue.