[grpc-io] Re: Cleanup bidi-stream from client that failed to start

In response stream observer onError() callback, you implement the cleanup logic for your application. The failed stream is cleaned up by itself, don't call any method of request observer then. On Tuesday, July 23, 2019 at 6:53:18 AM UTC-7, Joseph Vaughan wrote: > > By onClose, I meant

[grpc-io] Re: is it possible to use grpc's loadbalancing framework for active/passive?

You can look into enabling keepalive on the channel that will detect failure of underlying TCP connections and attempt to reconnect. If you have multiple TCP connections, gRPC will pick the first available connection by default and switch to another one when that one fails. On Monday, August

[grpc-io] How to pass data from rpc server call to server interceptor in java?

Hi all, I am trying to set some metadata after the rpc server call has been processed. The plan was to use server interceptor and override `close` method. Something like this: https://github.com/dconnelly/grpc-error-example/blob/master/src/main/java/example/Errors.java#L38 But the

[grpc-io] is it possible to use grpc's loadbalancing framework for active/passive?

hi.. i was wondering if it's possible to configure grpc's api to an active/passive config, so that if one packet doesn't come from one source in a defined gime, it would automatically switch to another source -- You received this message because you are subscribed to the Google Groups