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)

Solutions on the web

via Jive Software Open Source by Daniel Henninger, 1 year ago
via Jive Software Open Source by Daniel Henninger, 1 year ago
via JIRA by Daniel Henninger, 1 year ago
via xml-xindice-users by Todd Byrne, 1 year 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.ByteArrayOutputStream.writeTo(Unknown Source)	at net.sf.jml.net.Session.sendMessage(Session.java:511)	at net.sf.jml.net.Session.access$1300(Session.java:30)	at net.sf.jml.net.Session$MsgSender.run(Session.java:476)	at java.lang.Thread.run(Unknown Source)