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

Yes, this is on purpose, and is actually expected per the HTTP/2 spec . We recognize there are situations where that is not the correct behavior and more connections should be opened, although that point may be *before* hitting

[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