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.

Epoll native library timeout on WSL after upgrade from 4.1.42.Final to 4.1.43.Final

See original GitHub issue

Expected behavior

Http client requests issued via Spring WebTestClient should handle responses properly and not time out.

Actual behavior

WebTestClient times out after default 5 seconds

java.lang.IllegalStateException: Timeout on blocking read for 5000 MILLISECONDS
	at atoom.examples.reactor.netty.ReactorNettyTimeoutRegressionApplicationTest.testRequestResponse(ReactorNettyTimeoutRegressionApplicationTest.java:86)

Steps to reproduce

git clone https://github.com/atoom/reactor-netty-timeout-example.git && mvn test in WSL Windows 10 build <= 16299

Minimal yet complete reproducer code (or URL to code)

https://github.com/atoom/reactor-netty-timeout-example/tree/master

Netty version

4.1.43.Final

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

$ java -version
openjdk version "11.0.4" 2019-07-16 LTS
OpenJDK Runtime Environment Zulu11.33+15-CA (build 11.0.4+11-LTS)
OpenJDK 64-Bit Server VM Zulu11.33+15-CA (build 11.0.4+11-LTS, mixed mode)

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

C:\>systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 10 Enterprise
OS Version:                10.0.16299 N/A Build 16299

Issue Analytics

State:
Created 4 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

atoomcommented, Nov 14, 2019

@njhill Thanks for the information - I will close this issue and try to push for an update of Windows on our developer machines!

1reaction

atoomcommented, Nov 13, 2019

If we downgrade netty-transport-native-epoll to version 4.1.42.Final everything works as expected. We have also tried on newer versions of WSL (Windows 10 Build 17763) and that also solves this problem - however it will be quite a task for us to try to get an update of our corporate version of Windows 10 on all the developer machines.

Not sure how easy it is for a Netty developer to reproduce this error since it requires specific Windows versions. If more debug information is needed just let me know and I will try to produce it!