Dan Sirbu

I have changed my code to handle a bit differently the stream re-creation & I also added the keep alive. Again at the same 3rd iteration - this time the...

I think the error occurs because the grpc idle timeout value is 30s. And that would be close to 3 * ~10s retries .... If I increase that value to...

Shouldn't this call: ClientCalls.asyncBidiStreamingCall(this.getChannel().newCall(ConnectorServiceGrpc.getStartSessionMethod(), this.getCallOptions()), var1); reset the channel idle timeout if the connection has been lost and not established?

Thank you for your answer. It is a weird issue that I do not understand. I do not have set any keepalives - yet. I run all three 'parts' on...

I used the spring boot grpc project that expose the GrpcChannelConfigurer with which I can set the channelIdleTimeout. ```java public GrpcChannelConfigurer channelConfigurer() { return (channelBuilder, name) -> { LOGGER.info("Configuring grpc...

In the app I do not seem to see any specific setup. The app does not seem have any reference to MicrometerProducerListener when searching the java code. Uses: org.springframework.boot:spring-boot:jar:2.5.8:compile So...

I changed.the code of the app to use a thread pool. That solved the above. The consumer threads got limited as well as the micrometer ones. Due to work load...

....... when running a high no. of 'onRequest' then I end up having too many kafka consumer threads with the micrometer ones. If I pass to thread pool executor then...