I believe there's data integrity issue either from proxy or hardware that
using TLS can avoid, as notcarl@ said. Unless it can be reliably
reproduced, there is no way to investigate how this problem occurs for
plaintext.
On Wednesday, February 24, 2021 at 11:53:25 PM UTC-8 Ilya Pavlenko wrote:
Hi guys. We have recently had the same experience. The problem occurred
only under the heavy load and sometimes it took up to 2 hours to catch it.
As you recommended, enabling TLS resolved the problem.
Could you give any advice for the further investigation? And Y enabling ssl
so coordinately
And you are sure there is no proxy in between the client and server? One
thing that can cause this is data integrity issues, caused by networking
hardware. To protect against this, we always suggest using TLS (SSL).
I know this is more effort, but it would help indicate if there is errant
Yes, both are written in Java and I am using plaintext.
On Tuesday, September 18, 2018 at 7:58:16 PM UTC-4, Carl Mastrangelo wrote:
>
> Are both your client and server written using Java? Also, are you using
> TLS or plaintext?
>
> On Monday, September 17, 2018 at 8:21:30 PM UTC-7, Anthony
Are both your client and server written using Java? Also, are you using
TLS or plaintext?
On Monday, September 17, 2018 at 8:21:30 PM UTC-7, Anthony Corbacho wrote:
>
> Hi,
>
> This is strange I have enabled the same log but I only see RST_STREAM.
> Do I need to do something else?
>
> #
Hi,
This is strange I have enabled the same log but I only see RST_STREAM.
Do I need to do something else?
# GRPC debugging
log4j.logger.io.grpc.netty.NettyServerHandler=ALL
log4j.logger.io.grpc.netty.NettyClientHandler =ALL
On Monday, September 17, 2018 at 4:52:02 PM UTC-4, Carl Mastrangelo
Here's what i use to turn it
on: https://gist.github.com/carl-mastrangelo/49f6d6a8ff29200fcb7d9e25e473b2d0
On Monday, September 17, 2018 at 11:39:47 AM UTC-7, Anthony Corbacho wrote:
>
> Hi Carl,
>
> Thanks for the fast answer.
> How can I enable `netty debug log frame that's for DATA`?
>
>
Hi Carl,
Thanks for the fast answer.
How can I enable `netty debug log frame that's for DATA`?
thanks~.
On Monday, September 17, 2018 at 1:38:20 PM UTC-4, Carl Mastrangelo wrote:
>
> You should look for a netty debuglog frame that's for DATA, not
> RST_STREAM. That should show you the
You should look for a netty debuglog frame that's for DATA, not
RST_STREAM. That should show you the corrupted message.
There are also some hooks into the core gRPC library that (while more
complicated) will let you examine the message bytes. By using a custom
Marshaller, you can peak at
