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 GitHub by fdodino
, 1 year ago
This exception has no message.
via GitHub by javierfernandes
, 2 years ago
java.net.SocketException: Socket closed	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)	at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1877)	at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1786)	at java.io.ObjectOutputStream.reset(ObjectOutputStream.java:503)	at net.sf.lipermi.handler.ConnectionHandler.sendMessage(ConnectionHandler.java:182)	at net.sf.lipermi.handler.ConnectionHandler.remoteInvocation(ConnectionHandler.java:207)	at net.sf.lipermi.handler.CallProxy.invoke(CallProxy.java:58)	at com.sun.proxy.$Proxy49.getStackFrames(Unknown Source)	at org.uqbar.project.wollok.debugger.WollokDebugTarget.getStackFrames(WollokDebugTarget.java:310)	at org.uqbar.project.wollok.debugger.model.WollokThread.getStackFrames(WollokThread.java:34)	at org.uqbar.project.wollok.debugger.model.WollokThread.canStepReturn(WollokThread.java:156)	at org.eclipse.debug.internal.core.commands.StepReturnCommand.isSteppable(StepReturnCommand.java:27)	at org.eclipse.debug.internal.core.commands.StepCommand.isExecutable(StepCommand.java:46)	at org.eclipse.debug.core.commands.AbstractDebugCommand$UpdateJob.run(AbstractDebugCommand.java:101)	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)