https://bz.apache.org/bugzilla/show_bug.cgi?id=63191
--- Comment #15 from Boris Petrov <boris_pet...@live.com> ---
So, actually the bug is still here even on `9.0.29`, although maybe less often,
yes. Actually it happens mostly (only?) with Safari on Mac OS X, not that it
should matter. This is the stacktrace when running on `9.0.29` (there's a
billion threads blocked like this):
---------
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@13/Native Method)
- parking to wait for <0x000000068aacc300> (a
java.util.concurrent.CompletableFuture$Signaller)
at
java.util.concurrent.locks.LockSupport.park(java.base@13/LockSupport.java:194)
at
java.util.concurrent.CompletableFuture$Signaller.block(java.base@13/CompletableFuture.java:1867)
at
java.util.concurrent.ForkJoinPool.managedBlock(java.base@13/ForkJoinPool.java:3137)
at
java.util.concurrent.CompletableFuture.waitingGet(java.base@13/CompletableFuture.java:1894)
at
java.util.concurrent.CompletableFuture.get(java.base@13/CompletableFuture.java:2069)
at
org.cometd.websocket.server.WebSocketEndPoint.onMessage(WebSocketEndPoint.java:64)
at
org.cometd.websocket.server.WebSocketEndPoint.onMessage(WebSocketEndPoint.java:37)
at
org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:395)
at
org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:119)
at
org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:495)
at
org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:294)
at
org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:133)
at
org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:82)
at
org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171)
at
org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151)
at
org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148)
at
org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860)
at
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2022)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
- locked <0x000000068aacc440> (a
org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@13/ThreadPoolExecutor.java:1128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@13/ThreadPoolExecutor.java:628)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(java.base@13/Thread.java:830)
Not sure how to proceed. If you would like, we can reopen this (so you don't
forget it) and I'll be trying from time to time new versions to see what goes.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
