https://bz.apache.org/bugzilla/show_bug.cgi?id=66076
--- Comment #9 from Phil Clay <pil...@yahoo.com> ---
The test using the dev build unfortunately failed after about 3 hours with the
same symptom.
After it failed, a re-ran it with a breakpoint in NioEndpoint.flushNonBlocking
to see the new code in action, but my breakpoint unfortunately never gets hit
when sending outbound websocket messages.
(It does get hit when sending a normal HTTP response, so I can confirm the new
code is active and the breakpoint is working.)
Here's the partial stacktrace when SecureNioEndpoint.flush gets called (when it
doesn't write everything out). Perhaps that provides some visibility into why
NioEndpoint.flushNonBlocking is never called ?
Breakpoint reached
at
org.apache.tomcat.util.net.SecureNioChannel.flush(SecureNioChannel.java:123)
at
org.apache.tomcat.util.net.SecureNioChannel.write(SecureNioChannel.java:863)
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper$NioOperationState.run(NioEndpoint.java:1674)
at
org.apache.tomcat.util.net.SocketWrapperBase$OperationState.start(SocketWrapperBase.java:1063)
at
org.apache.tomcat.util.net.SocketWrapperBase.vectoredOperation(SocketWrapperBase.java:1482)
at
org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1408)
at
org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1379)
at
org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:93)
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:512)
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:398)
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendBytesByCompletion(WsRemoteEndpointImplBase.java:155)
at
org.apache.tomcat.websocket.WsRemoteEndpointAsync.sendBinary(WsRemoteEndpointAsync.java:65)
at
org.springframework.web.reactive.socket.adapter.StandardWebSocketSession.sendMessage(StandardWebSocketSession.java:92)
Should something in that stack be triggering NioEndpoint.flushNonBlocking
(either directly or indirectly via flushing the socket)?
--
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
