https://bz.apache.org/bugzilla/show_bug.cgi?id=63191

--- Comment #17 from Boris Petrov <boris_pet...@live.com> ---
Still happening on Tomcat 9.0.39 and CometD 5.0.1. It seemed to work for a day
or two (being accessed mostly from Chrome and Firefox) but then a connection
from Safari broke it again. Bot sure how this could be relevant but just
mentioning it. Here is the blocked thread's stack:

java.lang.Thread.State: WAITING (parking)
     at jdk.internal.misc.Unsafe.park(java.base@14.0.1/Native Method)
     - parking to wait for  <0x000000065a4c4ad8> (a
java.util.concurrent.CompletableFuture$Signaller)
     at
java.util.concurrent.locks.LockSupport.park(java.base@14.0.1/LockSupport.java:211)
     at
java.util.concurrent.CompletableFuture$Signaller.block(java.base@14.0.1/CompletableFuture.java:1860)
     at
java.util.concurrent.ForkJoinPool.managedBlock(java.base@14.0.1/ForkJoinPool.java:3137)
     at
java.util.concurrent.CompletableFuture.waitingGet(java.base@14.0.1/CompletableFuture.java:1887)
     at
java.util.concurrent.CompletableFuture.get(java.base@14.0.1/CompletableFuture.java:2062)
     at
org.cometd.server.websocket.javax.WebSocketEndPoint.onMessage(WebSocketEndPoint.java:64)
     at
org.cometd.server.websocket.javax.WebSocketEndPoint.onMessage(WebSocketEndPoint.java:37)
     at
org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:402)
     at
org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:119)
     at
org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:502)
     at
org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:301)
     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:868)
     at
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:1991)
     at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
     - locked <0x000000065a4c4c18> (a
org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper)
     at
java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@14.0.1/ThreadPoolExecutor.java:1130)
     at
java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@14.0.1/ThreadPoolExecutor.java:630)
     at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
     at java.lang.Thread.run(java.base@14.0.1/Thread.java:832)

-- 
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

Reply via email to