java.net.SocketException

tip

Upgrade your docker-selenium

tip

Client closed the websocket connection (safe to ignore)

tip

*not english*


poroszdporoszd
tip

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

tip

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

tip

Upgrade your nanohttpd

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

tip

Upgrade yokozuna

tip

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

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

  • Remote Apache 2.0 server
    via by Olav Slåtta,
  • IllegalStateException:response already commited
    via by Unknown author,
  • weblogic.common.ResourceException: DataSource
    via by Unknown author,
    • java.net.SocketException: Connection aborted by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(Unknown Source)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    152 more bugmates