-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.3.14.Final, 2.2.33.Final
-
None
There appears to be a regression in 2.3.14.Final. stop() processing hangs when start() of an Undertow instance with multiple HTTP listeners has failed due to a port clash. The stack trace of the hang is the following:
"main" #1 prio=5 os_prio=31 cpu=579.71ms elapsed=10.66s tid=0x00007f950a008e00 nid=0x2103 waiting on condition [0x0000700002d2c000] java.lang.Thread.State: WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@17.0.11/Native Method) at java.util.concurrent.locks.LockSupport.park(java.base@17.0.11/LockSupport.java:341) at org.xnio.nio.WorkerThread$SelectNowTask.doWait(WorkerThread.java:915) at org.xnio.nio.WorkerThread.cancelKey(WorkerThread.java:793) at org.xnio.nio.NioHandle.cancelKey(NioHandle.java:91) at org.xnio.nio.NioTcpServer.close(NioTcpServer.java:261) at org.xnio.nio.QueuedNioTcpServer2.close(QueuedNioTcpServer2.java:126) at org.xnio.IoUtils.safeClose(IoUtils.java:152) at io.undertow.Undertow.stop(Undertow.java:262) - locked <0x000000061e400680> (a io.undertow.Undertow) at com.example.UndertowTests.startWithPortClashOnSecondHttpListenerThrowsRuntimeException(UndertowTests.java:28)
The problem does not occur with 2.3.13.Final.
- is blocked by
-
XNIO-435 Revert XNIO-385
-
- Pull Request Sent
-