Error "html: Servlet error - java.io.IOException: Broken pipe"

Metalink id
-----------

Error "html: Servlet error - java.io.IOException: Broken pipe" in oacore application.log. (Doc ID 1631624.1)

Below errors are recording in application.log
---------------------------

15/03/27 09:24:52.838 html: Servlet error
java.io.IOException: Connection reset by peer
        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:69)
        at sun.nio.ch.IOUtil.write(IOUtil.java:40)
        at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:336)
        at java.nio.channels.Channels.writeFullyImpl(Channels.java:59)
        at java.nio.channels.Channels.writeFully(Channels.java:81)
        at java.nio.channels.Channels.access$000(Channels.java:47)
        at java.nio.channels.Channels$1.write(Channels.java:155)
        at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
        at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
        at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
        at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
        at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
        at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
        at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
        at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
        at java.lang.Thread.run(Thread.java:662)


Cause
+++++
The errors are caused by writing to a connection when the other end has already closed it.
Basically, this is caused by the peer unexpectedly ending the connection (for instance, by closing the browser during an HTTP connection).
When user closes the client session, server cannot write any streams to that client and generates this error.
If you click in a link and before the page is rendered you click in a second one. the first request is canceled and you will see a broken pipe at that time.

 Solution
+++++++
This is normal behavior.
This message can be ignored if you does not face login, disconnection or performance issue.