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

tomcat-dev | Konstantin Kolinko | 3 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Re: [VOTE] Release Apache Tomcat 7.0.52

    apache.org | 1 year ago
    java.io.IOException: Unable to write the complete message as the WebSocket connection has been closed
  2. 0

    Tomcat - Dev - [VOTE] Release Apache Tomcat 7.0.52

    nabble.com | 6 months ago
    java.io.IOException: Unable to write the complete message as the WebSocket connection has been closed
  3. 0

    Re: [VOTE] Release Apache Tomcat 7.0.52

    tomcat-dev | 3 years ago | Konstantin Kolinko
    java.io.IOException: Unable to write the complete message as the WebSocket connection has been closed
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      Unable to write the complete message as the WebSocket connection has been closed

      at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString()
    2. Tomcat WS
      TestWsWebSocketContainer.testSmallTextBufferClientTextMessage
      1. org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:219)
      2. org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:162)
      3. org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
      4. org.apache.tomcat.websocket.TestWsWebSocketContainer.doBufferTest(TestWsWebSocketContainer.java:258)
      5. org.apache.tomcat.websocket.TestWsWebSocketContainer.testSmallTextBufferClientTextMessage(TestWsWebSocketContainer.java:157)
      5 frames