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

    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)

  2. ,
    via GitHub by ppoulard

    before running my test in debug mode, i open the debug view, and remove some breakpoints (such as some remaining on NullPointersExceptions, and Sockets)

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 sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)	at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)	at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)	at java.io.BufferedWriter.flush(BufferedWriter.java:254)