Bumped grpc-netty from 1.5.0 to 1.6.1, which bumped netty from 4.1.12.Final
to 4.1.14. Final. Fixed the problem for me.
For the curious, it seemed like a bug in KeepAliveManager, sending, in
certain situations, 2 pings at a time instead of 1. Luckily, the netty team
already fixed it.
Keep up t
What does "increase the limit on the server side" mean? I configured a
client and server as:
private val channel = NettyChannelBuilder
.forAddress("localhost", StrawmanServer.Port)
.usePlaintext(true)
.keepAliveTime(10, TimeUnit.SECONDS)
.keepAliveTimeout(5, TimeUnit.SECONDS)
Seems to me that there should be an autoback off. Server warning don't
call back again for 4 min . Well behaved clients follow that, bad ones get
disconnected.
On Monday, June 5, 2017 at 7:17:30 PM UTC-4, Eric Anderson wrote:
>
> In 1.3 we started allowing clients to be more aggressive. From
In 1.3 we started allowing clients to be more aggressive. From the 1.3
release notes:
"Keepalives in Netty and OkHttp now allow sending pings without outstanding
RPCs. The minimum keepalive time was also reduced from 1 minute to 10
seconds. Clients must get permission from the services they use be
Hi
I set on a grpc stream with NettyChannel options:
keepAliveTime"(60L, TimeUnit.SECONDS});
keepAliveTimeout{8L, TimeUnit.SECONDS});
At times in the code I've added sleep for 15 min. I see on Wireshark the
keep alives.
But after a time I see :
---
