Ahh I see! Thank you very much
On Friday, September 22, 2017 at 11:43:50 AM UTC-7, Josh Humphries wrote:
>
> Headers are per stream, not per message. The whole stream is a single HTTP
> round-trip. So the first thing the server sends back are response headers.
> Then the response payload (which
Headers are per stream, not per message. The whole stream is a single HTTP
round-trip. So the first thing the server sends back are response headers.
Then the response payload (which consists of zero or more messages).
Finally, you get trailers.
To include metadata for each response message,
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
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)
