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.

java.lang.IllegalStateException: failed to create a child event loop (facing sporadic issue)

See original GitHub issue

ava.lang.IllegalStateException: failed to create a child event loop at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:88) ~[netty-common-4.1.25.Final.jar:4.1.25.Final] at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:58) ~[netty-common-4.1.25.Final.jar:4.1.25.Final] at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:47) ~[netty-common-4.1.25.Final.jar:4.1.25.Final] at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:59) ~[netty-transport-4.1.25.Final.jar:4.1.25.Final] at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:77) ~[netty-transport-4.1.25.Final.jar:4.1.25.Final] at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:72) ~[netty-transport-4.1.25.Final.jar:4.1.25.Final] at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:59) ~[netty-transport-4.1.25.Final.jar:4.1.25.Final] at reactor.ipc.netty.resources.DefaultLoopResources.<init>(DefaultLoopResources.java:70) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at reactor.ipc.netty.resources.DefaultLoopResources.<init>(DefaultLoopResources.java:57) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at reactor.ipc.netty.resources.LoopResources.create(LoopResources.java:83) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at org.cloudfoundry.reactor._DefaultConnectionContext.getThreadPool(_DefaultConnectionContext.java:233) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext.access$2601(DefaultConnectionContext.java:25) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext$InitShim.getThreadPool(DefaultConnectionContext.java:215) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext.getThreadPool(DefaultConnectionContext.java:415) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor._DefaultConnectionContext.lambda$getHttpClient$5(_DefaultConnectionContext.java:104) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at reactor.ipc.netty.http.client.HttpClient.<init>(HttpClient.java:135) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at reactor.ipc.netty.http.client.HttpClient.<init>(HttpClient.java:63) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at reactor.ipc.netty.http.client.HttpClient$Builder.build(HttpClient.java:461) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at reactor.ipc.netty.http.client.HttpClient.create(HttpClient.java:86) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE] at org.cloudfoundry.reactor._DefaultConnectionContext.getHttpClient(_DefaultConnectionContext.java:101) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext.access$2001(DefaultConnectionContext.java:25) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext$InitShim.getHttpClient(DefaultConnectionContext.java:117) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext.<init>(DefaultConnectionContext.java:76) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext.<init>(DefaultConnectionContext.java:25) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na] at org.cloudfoundry.reactor.DefaultConnectionContext$Builder.build(DefaultConnectionContext.java:1041) ~[cloudfoundry-client-reactor-3.12.0.RELEASE.jar:na]

Issue Analytics

State:
Created 5 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

parasuram-tanguturucommented, Jan 31, 2019

after increasing ulimit we didn’t faced this issue as of now . thank you for quick response.

1reaction

nebhalecommented, Jan 24, 2019

@parasuramln We believe that the problem is resource exhaustion but can only tell for sure with output from those two commands (ulimit and lsof | wc -l). You’ll need to get shell access to the container where your application is having trouble, at the time your application is having trouble, and execute those commands. The “Ulimits - not configured” output isn’t accurate because Linux always has a ulimit configured even if it just the default.

Top Results From Across the Web

intellij idea - Failed to create a child event loop - Stack Overflow

I'm using Windows 8.1 with Anti-virus program Windows Defender . Error detail from Log file: java.lang.IllegalStateException: failed to create a child event ......

java.lang.IllegalStateException: failed to create a child event ...

Startup error: java.lang.IllegalStateException: failed to create a child event loop. Relates to 1. Relates to 1 issue (0 unresolved).

Failed to create a child event loop - Inductive Automation Forum

IllegalStateException: java.lang.IllegalStateException: failed to create a child event loop. Could you please help me about this issue.

Fix list for IBM WebSphere Application Server V8.5

IBM WebSphere Application Server provides periodic fixes for the base and Network Deployment editions of release V8.5. The following is a complete listing ......

Livy Starts Throwing Java.Lang.Illegalstateexception: Failed To

scalaXB Async Dispatcher java.lang.IllegalStateException: failed to create a child event loop.Configure Scalaxb SBT Plugin's Generated Source Code Location.