tip

Set larger socket timeout (or 0 to set no timeout).

via GitHub by ritchieGitHub
tip

Upgrade your nanohttpd

via github.com by Unknown author
tip

Here is a animation for the life cycle. http://tcp.cs.st-andrews.ac.uk/index.shtml?page=connection_lifecycle

tip

Upgrade your docker-selenium

via github.com by Unknown author
tip

Client closed the websocket connection (safe to ignore)

via github.com by Unknown author
tip

*not english*

tip

Nginx does not handle websocket requests. Configure nginx proxy for websockets.

via GitHub by nathandunn
tip

It takes too long time for the JVM to find enough entropy for secure connection. Use this jvm option: '-Djava.security.egd=file:/dev/./urandom'.

via GitHub by zxqfox
tip

Upgrade yokozuna

via github.com by Unknown author

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • Unexpected JDBC Connection closed
    via Google Groups by thenrick,
  • Unexpected connection is closed
    via Oracle Community by 843854,
  • Tomcat 4.0 throws a SocketException (wondering why:p)
    via Google Groups by Luis,
  • Tomcat socket closed error
    via Oracle Community by 807596,
  • broken pipe error
    via Oracle Community by 843841,
  • Apache 2.x + Tomcat 4.x + Load Balancing
    via Coderanch by Narsimha Manekar,
  • some socket question
    via Google Groups by Joe Wong,
  • Users with the same issue

    Alireza Mohamadi2 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    129 more bugmate user