High CPU from org.xnio._private.Messages_$logger.connectionClosedEarly calls in EAP 7's I/O threads

Solution In Progress - Updated -

Issue

  • JBoss EAP 7 reaches high CPU and its I/O threads persist with high CPU in calls like below:
"default I/O-31" #152 prio=5 os_prio=0 tid=0x0000562ec5b22800 nid=0xce7d runnable [0x00007ff48858f000]
   java.lang.Thread.State: RUNNABLE
        at java.lang.Throwable.fillInStackTrace(Native Method)
        at java.lang.Throwable.fillInStackTrace(Throwable.java:784)
        - locked <0x000000062e9ff4f0> (a java.io.EOFException)
        at java.lang.Throwable.<init>(Throwable.java:266)
        at java.lang.Exception.<init>(Exception.java:66)
        at java.io.IOException.<init>(IOException.java:58)
        at java.io.EOFException.<init>(EOFException.java:62)
        at org.xnio._private.Messages_$logger.connectionClosedEarly(Messages_$logger.java:669)
        at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:416)
        at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:400)
        at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
        at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
        at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1254)
        at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
        at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content