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

Samebug tips

  1. ,
    via github.com by Unknown author

    Upgrade your docker-selenium

  2. ,
    via github.com by Unknown author

    Probably there is a bug in TestNG Eclipse plugin (6.8.6.20130607_0745), try an other version (e.g. 6.8.0.20121120_1820)

Solutions on the web

via Oracle Community by 843790, 1 year ago
via Oracle Community by 843790, 1 year ago
via Oracle Community by 807545, 6 months ago
java.net.SocketException: Broken pipe	at java.net.SocketOutputStream.socketWrite0(Native Method)	at java.net.SocketOutputStream.socketWrite(Unknown Source)	at java.net.SocketOutputStream.write(Unknown Source)	at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)	at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)	at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)	at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)	at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)	at java.io.ObjectOutputStream.writeObject0(Unknown Source)	at java.io.ObjectOutputStream.writeFatalException(Unknown Source)	at java.io.ObjectOutputStream.writeObject(Unknown Source)	at Vdb.SlaveSocket.putMessage(SlaveSocket.java:278)	at Vdb.CollectSlaveStats.(CollectSlaveStats.java:121)	at Vdb.Reporter.run(Reporter.java:183)