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

Solutions on the web

via Google Groups by Scott Nichol, 1 year ago
via Google Groups by Matthew Ward, 2 years ago
connection error; reason: {#method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0), null, "[B@275e538e"}
via Google Groups by CJ, 11 months ago
connecti on error; reason: {#method<connection.close>(reply-code=320, reply-text=CONNECTI ON_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0), null, ""}
via flume-user by Suresh V, 9 months ago
connection error
via incubator-flume-user by Suresh V, 1 month ago
connection error
via GitHub by HardikkumarSoni
, 7 months ago
clean connection shutdown; protocol method: #method<connection.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
java.net.SocketException: Connection reset	at java.net.SocketInputStream.read(SocketInputStream.java:196)	at java.net.SocketInputStream.read(SocketInputStream.java:122)	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)	at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288)	at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:95)	at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:139)	at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:538)	at java.lang.Thread.run(Thread.java:745)