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 Oracle Community by 392 Guest, 1 year ago
java.io.IOException: Broken pipe	at sun.nio.ch.FileDispatcher.write0(Native Method)	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)	at sun.nio.ch.IOUtil.write(IOUtil.java:75)	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)	at com.sun.enterprise.web.connector.grizzly.OutputWriter.flushChannel(OutputWriter.java:92)	at com.sun.enterprise.web.connector.grizzly.OutputWriter.flushChannel(OutputWriter.java:65)	at com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:170)	at com.sun.enterprise.web.connector.grizzly.async.AsynchronousOutputBuffer.flushChannel(AsynchronousOutputBuffer.java:81)	at com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:203)	at com.sun.enterprise.web.connector.grizzly.async.AsynchronousOutputBuffer.flushBuffer(AsynchronousOutputBuffer.java:113)	at com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flush(SocketChannelOutputBuffer.java:181)	at com.sun.enterprise.web.connector.grizzly.async.AsynchronousOutputBuffer.flush(AsynchronousOutputBuffer.java:103)	at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.action(DefaultProcessorTask.java:1059)	at org.apache.coyote.Response.action(Response.java:237)	at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:382)