INTERNAL: Encountered end-of-stream mid-frame

[mohit-0109]

We're encountering an 'INTERNAL: Encountered end-of-stream mid-frame' error on our gRPC client.
Our setup details are:
gRPC Version: 1.60.1
Netty: grpc-netty-shaded bundling Netty 4.1.100.Final
Client Stub: blockingStub
I'm aware of the known gRPC-Java issues with Netty 4.1.111.Final that were subsequently fixed in gRPC 1.65.0+.
My core question is: Could this 'end-of-stream mid-frame' error be indicative of an underlying gRPC-Java/Netty incompatibility or bug in version 1.60.1 (even with Netty 4.1.100.Final), or is it more likely a symptom of genuine network issues like packet loss on the client side?

Any insights into the most probable causes would be greatly appreciated.

[shivaspeaks]

The "end-of-stream mid-frame" error means that the client received an indication that the HTTP/2 stream was ending in the middle of a data frame. It's essentially a transport-level error which is handled by Netty, that gRPC is propagating up to your application.

Do you have any steps to reproduce the issue? Without being able to reproduce it, it's hard to be certain, but upgrading is often the easiest way to rule out.

[mohit-0109]

Unfortunately the issue is not reproducible, its a very rare case. But can confirm that there was a network issue which occurred during the instance i saw the error.

[AgraVator]

Hi @mohit-0109, closing this for now. Feel free to reopen if you have anything new on it.

[zt9788]

Unfortunately the issue is not reproducible, its a very rare case. But can confirm that there was a network issue which occurred during the instance i saw the error.

I also encountered this problem when using springboot2 (netty4.1.101+-) with grpc 1.75+, but when calling springboot3 (netty4.1.127+-), this issue occurred (I tested using grpc 1.74 in springboot2 is ok)