Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No logging of byte distribution write error

See original GitHub issue

Expected behavior

Print t throwable when a writer error is thrown.

Line here:

https://github.com/netty/netty/blob/201f6b6bb2dcdff07df6e30552b96fedbcf21759/codec-http2/src/main/java/io/netty/handler/codec/http2/WeightedFairQueueByteDistributor.java#L614

Actual behavior

When a writer error is thrown the error message is “byte distribution write error” but the t throwable is not printed.

io.grpc.StatusRuntimeException: INTERNAL: Connection closed after GOAWAY. HTTP/2 error code: INTERNAL_ERROR, debug data: byte distribution write error
	at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:262)
	at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:243)
	at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:156)
	at com.rachio.user.api.user.UserServiceGrpc$UserServiceBlockingStub.getVisibleElements(UserServiceGrpc.java:4110)
	at com.rachio.user.UserClientWrapper.getVisibleElements(UserClientWrapper.java)
	at com.rachio.api.service.grpc.LocationServiceImpl.getLocationVisibleElement(LocationServiceImpl.java:131)
	at com.rachio.api.service.grpc.LocationServiceImpl.getLocation(LocationServiceImpl.java:122)
	at com.rachio.api.service.grpc.LocationServiceImpl.getLocation(LocationServiceImpl.java:115)
	at com.rachio.api.service.grpc.LocationServiceImpl$$FastClassBySpringCGLIB$$3783b184.invoke(<generated>)

Steps to reproduce

I really don’t know. We see this randomly with Grpc. Would love to know what is actually causing this.

Minimal yet complete reproducer code (or URL to code)

Netty version

io.netty 4.1.73.Final jetty-9.4.z-SNAPSHOT

JVM version (e.g. `java -version`)

1.8.0_332

OS version (e.g. `uname -a`)

Fargate Linux 1.4.0

Issue Analytics

State:
Created a year ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

ejona86commented, Jun 9, 2022

Closing, but open an issue on grpc/grpc-java.

0reactions

fgarsombkecommented, Jun 9, 2022

Ok thank you both! So if ultimately due to log spam, should I close the ticket?

Top Results From Across the Web

Logspam from Netty if sending when cancelled #6943 - GitHub

I expect to see no unnecessary logs. ... Error gets logged here: ... No logging of byte distribution write error netty/netty#12443.

"Failed to write x bytes to file 'x'... (Server message 305419896 ...

(Server message 305419896) No space left on device (Linux Standard C Library error 28)" appears in the DSSerrors.log in MicroStrategy 9.x and 10 ......

Can write(2) return 0 bytes written*, and what to do if it does?

My take would be 'report it as an error via the appropriate logging mechanism and return value' and see whether it is actually...

Error : INCORRECT_SIZE Vdbench determined that not ...

Hi ,. Not sure i understand the reason for this error , it all fell apart in the format area what was he...

I get an error: could not write bytes: Broken pipe - Ask Ubuntu

and then quickly return to the Login window. But I can log in as Guest. I only remember that I have tried to...