[grpc-io] Re: Java grpc client behaviour on hitting H/2 max concurrent streams

Hi Gaurav, For Java you might find useful the GAX channel pool: https://github.com/googleapis/gax-java https://github.com/googleapis/gax-java/blob/master/gax-grpc/src/main/java/com/google/api/gax/grpc/ChannelPool.java -- Yuri On Tuesday, June 15, 2021 at 10:22:24 PM UTC-7 gpoo...@stripe.com wrote

[grpc-io] Java grpc client behaviour on hitting H/2 max concurrent streams

Hello! I have a situation where the server sets H/2 max concurrent streams intentionally low (e.g. 16 or 32) for good reason (that are somewhat orthogonal to gRPC so I will skip the details) The behavior I seem to be observing is that Java gRPC client stalls when it hits that limit and waits for

Re: [grpc-io] Re: gRPC occasionally appears abnormal

Hi, UNAVAILABLE is one of the gRPC status codes, like 503 in HTTP status code. You can read more about the gRPC status code at https://github.com/grpc/grpc/blob/master/doc/statuscodes.md. What you are experiencing could have many different causes. I would recommend tuning up the Java client's log

[grpc-io] grpc-dotnet on Xamarin.Android

We saw the announcement that Grpc.Core will be deprecated now. We have the use case to run a gRPC service hosted in an Android application. With Grpc.Core, that's easily possible, since monoandroid90 supports netstandard2.1. We saw, that Grpc.AspNetCore.Server needs netcoreapp3.0 or net5.0 as