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 db-derby-user by Erick Lichtas, 1 year ago
via Stack Overflow by user2278118
, 2 years ago
Connection reset by peer: socket write error
via Stack Overflow by user1494517
, 2 years ago
Connection reset by peer: socket write error
via Oracle Community by 2726310, 1 year ago
Connection reset by peer: socket write error
via Stack Overflow by An Alien
, 2 years ago
via Stack Overflow by Dreik
, 1 year ago
java.net.SocketException: Connection reset by peer: socket write error	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(UnknownSource)	at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(UnknownSource)	at java.io.ObjectOutputStream.reset(Unknown Source)	at org.apache.derby.impl.store.replication.net.SocketConnection.writeMessage(Unknown Source)	at org.apache.derby.impl.store.replication.net.ReplicationMessageTransmit.sendMessage(Unknown Source)	at org.apache.derby.impl.store.replication.master.AsynchronousLogShipper.shipALogChunk(Unknown Source)	at org.apache.derby.impl.store.replication.master.AsynchronousLogShipper.run(Unknown Source)