-
Bug
-
Resolution: Done
-
Major
-
3.4.0.Beta1
-
None
I/O threads are left in a busy state causing maximum CPU load after a REST service has been invoked.
"default I/O-5" 96 prio=5 os_prio=0 tid=0x000000005bc59000 nid=0x20d0 runnable [0x000000006269f000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- locked <0x00000000c90da9c0> (a sun.nio.ch.Util$2)
- locked <0x00000000c90da9b0> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000000c90da860> (a sun.nio.ch.WindowsSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:506)