Connection reset by peer: socket write error

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

via by Unknown author

Probably there is a bug in TestNG Eclipse plugin (, try an other version (e.g.

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 GitHub by xingzhefeng
, 11 months ago
Connection reset by peer: socket write error
via by Unknown author, 1 year ago
via Oracle Community by 843842, 1 year ago
Connection reset by peer: socket write error
via Coderanch by surlac surlacovich, 1 year ago
Software caused connection abort: socket write error
via Stack Overflow by karthi
, 2 years ago
via Google Groups by Sunny Kumar, 2 years ago
Software caused connection abort: socket write error Connection reset by peer: socket write error
at Method)
at kafka_clj.tcp_api$write_BANG_.invokeStatic(tcp_api.clj:14)
at kafka_clj.tcp_api$write_BANG_.doInvoke(tcp_api.clj:10)
at clojure.lang.RestFn.invoke(
at kafka_clj.produce$send_messages.invokeStatic(produce.clj:192)
at kafka_clj.produce$send_messages.invoke(produce.clj:175)
at kafka_clj.produce$send_messages.invokeStatic(produce.clj:181)
at kafka_clj.produce$send_messages.invoke(produce.clj:175)
at kafka_clj.client$send_messages.invokeStatic(client.clj:287)
at kafka_clj.client$send_messages.invoke(client.clj:282)
at kafka_clj.client$send_data.invokeStatic(client.clj:298)
at kafka_clj.client$send_data.invoke(client.clj:291)
at kafka_clj.client$handle_async_topic_messages.invokeStatic(client.clj:322)
at kafka_clj.client$handle_async_topic_messages.invoke(client.clj:318)
at kafka_clj.client$async_handler$fn__10902$fn__10911.invoke(client.clj:336)
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Users with the same issue

4 times, 19 hours ago
Once, 5 days ago
Once, 6 days ago
Once, 3 weeks ago
30 times, 4 weeks ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.