[ https://issues.apache.org/jira/browse/CXF-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731874#comment-17731874 ]
Lars Uffmann commented on CXF-8885: ----------------------------------- Here is a relevant thread dump from an affected application running 3.6.0 {noformat} "HttpClient-75-SelectorManager" #3340 daemon prio=5 os_prio=0 cpu=3043.60ms elapsed=331383.65s tid=0x00007ffb9351d9d0 nid=0xd78 runnable [0x00007ffb890cc000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPoll.wait(java.base@17.0.6/Native Method) at sun.nio.ch.EPollSelectorImpl.doSelect(java.base@17.0.6/EPollSelectorImpl.java:118) at sun.nio.ch.SelectorImpl.lockAndDoSelect(java.base@17.0.6/SelectorImpl.java:129) - locked <0x00000000d6187b88> (a sun.nio.ch.Util$2) - locked <0x00000000d6187b38> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(java.base@17.0.6/SelectorImpl.java:141) at jdk.internal.net.http.HttpClientImpl$SelectorManager.run(java.net.http@17.0.6/HttpClientImpl.java:889) {noformat} > HttpClient SelectorManager threads run indefinitely causing OOM > --------------------------------------------------------------- > > Key: CXF-8885 > URL: https://issues.apache.org/jira/browse/CXF-8885 > Project: CXF > Issue Type: Bug > Components: Transports > Affects Versions: 4.0.0, 3.6.0 > Reporter: Cardo Eggert > Priority: Major > Attachments: image (5).png > > > Probably caused by https://issues.apache.org/jira/browse/CXF-8840 . > Started to notice that when updating from 3.5.x to 3.6.0 that our servers > started getting OOM. Noticed from the resulting logs that a lot of threads > were active that were in the format > HttpClient-<NR>-SelectorManager > when reverted to 3.5.6 then it did not occur anymore. > > Tried to use VirtualVM when debugging it and saw when the thread was started, > it never died, basically meaning that it ran indefinitely. OOM happened when > there were about over 1000 of these threads. -- This message was sent by Atlassian Jira (v8.20.10#820010)