java.io.IOException: Unable to write the complete message as the WebSocket connection has been closed

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via apache.org by Unknown author, 2 years ago
Unable to write the complete message as the WebSocket connection has been closed
via tomcat-dev by Konstantin Kolinko, 1 year ago
Unable to write the complete message as the WebSocket connection has been closed
via nabble.com by Unknown author, 1 year ago
Unable to write the complete message as the WebSocket connection has been closed
java.io.IOException: Unable to write the complete message as the WebSocket connection has been closed
at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:423)
at org.apache.tomcat.websocket.WsSession.close(WsSession.java:394)
at org.apache.tomcat.websocket.WsFrameClient.close(WsFrameClient.java:82)
at org.apache.tomcat.websocket.WsFrameClient.access$300(WsFrameClient.java:26)
at org.apache.tomcat.websocket.WsFrameClient$WsFrameClientCompletionHandler.completed(WsFrameClient.java:111)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:206)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.