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 java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)	at io.nats.client.ConnectionImpl.processOpError(ConnectionImpl.java:672)	at io.nats.client.ConnectionImpl.processPingTimer(ConnectionImpl.java:1591)	at io.nats.client.ConnectionImpl$11.run(ConnectionImpl.java:1559)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)	at java.lang.Thread.run(Thread.java:745)	at io.nats.client.NATSThread.run(NATSThread.java:63)