High CPU Usage WildFly 26 and Java 17

[Sascha Janz]

We are using WildFly 26.1.3 and Java 17.0.12+7

Today we got high CPU usage on one of our systems.

we analyzed some stacktraces and found some suspect threads with the following stacktrace

"default I/O-1" #114 prio=5 os_prio=0 cpu=125875.00ms elapsed=1114866.91s tid=0x0000025943cefd60 nid=0xdf4 runnable  [0x000000c46effe000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.WEPoll.wait(java...@17.0.12/Native Method)
at sun.nio.ch.WEPollSelectorImpl.doSelect(java...@17.0.12/WEPollSelectorImpl.java:111)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(java...@17.0.12/SelectorImpl.java:129)
- locked <0x00000002a4051850> (a sun.nio.ch.Util$2)
- locked <0x00000002a40517f0> (a sun.nio.ch.WEPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(java...@17.0.12/SelectorImpl.java:141)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:551)

is this a known bug? 

i found a reference to My Oracle Support Doc ID 2934851.1., but unfortunatlely got no access.

Thanks for help.

regards
Sascha

[Jose Socola]

Hi, 

Wildfly 26 isn't certified for JDK 17, but you try to update all these JAR files in modules that refer to netty to 4.1.116 and undertown to 2.2.37. It worked well for us with JDK 17 when we had CPU issues.

$wildfly/modules/system/layers/base/io/netty

$wildfly/modules/system/layers/base/io/undertown

$wildfly/modules/system/layers/base/org/jboss

Regards,

JS

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/a08c865d-5cc2-4ff5-bb04-7592503d05e8n%40googlegroups.com.

[Sascha Janz]

Hi,

thank you so much. we did the update like you descibed and the problem went away.  i think it took quite a lot of time to get the right combination of jars... 

Regards

Sascha