Re: [grpc-io] Re: Java GRPC async - io.grpc.StatusRuntimeException: CANCELLED

This sounds like auto-cancellation. When a RPC completes on the server, the server's io.grpc.Context is cancelled. That propagates to any outgoing RPCs. This is the same wiring that will cancel those RPCs when the initial RPC is cancelled and provides deadline propagation. I think you want to run

Re: [grpc-io] Re: [java] Logging result of every call on server

This was also discussed at https://stackoverflow.com/a/47025228/4690866 . Yes, ServerCall.close() is not guaranteed. The only guarantee is you'll get one of onCancel or onComplete. onComplete should only happen after a call to ServerCall.close(). On Tue, Oct 31, 2017 at 12:46 PM, John Hume

[grpc-io] [C++] Modifying rpc url paths

Hi, Currently, looks like rpc urls are generated in the form of //. Is there a way to prefix the urls such that grpc client could call //? The receiver can chop off the prefix and call the correct rpc. Use case: We'd like to have a proxy sitting between our client and grpc server. The proxy

Re: [grpc-io] Re: [grpc-java] All RPCs failed with DEADLINE_EXCEEDED

All the methods should be overriden. The idle connection time is likely that timeout. On Monday, October 30, 2017 at 2:00:59 PM UTC-7, bira...@gmail.com wrote: > > Some findings to share, not sure if related though: > 1. we use custom grpc name resolver, and refresh() method is not >

Re: [grpc-io] Re: grpc.max_connection_age_ms for client config?

Thanks for the information. Apologies for my previous message, which was follow-up on a completely different question. (I thought I'd asked it in this group, but apparently not.) On Wednesday, November 1, 2017 at 11:36:34 AM UTC-5, Eric Anderson wrote: > > grpc.max_connection_age_ms is a

Re: [grpc-io] Re: grpc.max_connection_age_ms for client config?

grpc.max_connection_age_ms is a server-side option. For documentation, see gRFC A9 Server-side Connection Management . This should work on server-side without issue. If you're concerned about resources, use

[grpc-io] [c++] Hanging calls on Windows

Hi, I have encountered two situations where a blocking call never returns (or after at least ~10 minutes I have lost patience and killed the client process). Situation 1) I open a channel to an embedded device that is NOT grpc enabled and talks an proprietary TCP protocol instead. Instead of

[grpc-io] Re: [grpc-c++] sample cmake makefile for windows

cmake is the official way to build gRPC on Windows - so we do have an official CMakeLists.txt file in our repository and we also have instructions how to build: https://github.com/grpc/grpc/blob/master/INSTALL.md#building-using-cmake-recommended We do have tests running continously for cmake

[grpc-io] Re: [grpc-c++] gRPC polling for incoming packets from multiple sockets

Hi, Thanks a lot for providing the accomplish able approach towards it. Yes, I am also using C++ gRPC. I was carefully following this concrete example -- https://github.com/grpc/grpc/tree/master/examples/cpp/helloworld On the server you get a completion queue in this line -- *auto cq =

[grpc-io] Re: Close channels from Server sides

@Carl: Great advice! Thank you. On Wednesday, November 1, 2017 at 12:19:03 AM UTC+7, Carl Mastrangelo wrote: > > On the server side you can set NettyServerBuilder.maxConnectionAge() and > related methods to limit how long idle clients are connected. > > On Monday, October 30, 2017 at 8:41:06 PM