org.apache.logging.log4j.core.appender.AppenderLoggingException

Error writing to TCP:localhost:601

Samebug tips13

Upgrade your docker-selenium

Client closed the websocket connection (safe to ignore)

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web58

  • via logging-log4j-user by Blake Day, 9 months ago
    Error writing to TCP:localhost:601
  • via logging-log4j-user by Ralph Goers, 9 months ago
    Error writing to TCP:localhost:601
  • via logging-log4j-user by Blake Day, 9 months ago
    Error writing to TCP:localhost:601
  • Stack trace

    • org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to TCP:localhost:601 at org.apache.logging.log4j.core.net.TcpSocketManager.write(TcpSocketManager.java:140) at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:136) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:105) at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:152) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:125) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:116) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) at org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.callAppenders(AsyncAppender.java:308) at org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:261) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) at java.net.SocketOutputStream.write(SocketOutputStream.java:153) at org.apache.logging.log4j.core.net.TcpSocketManager.write(TcpSocketManager.java:131) ... 8 more

    Write tip

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

    Users with the same issue

    Once, 5 months ago
    Unknown user
    Once, 7 months ago
    7 times, 7 months ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 11 months ago
    254 more bugmates