The applicationlog of the OA core reports brokenpipe.

The application log of the background OA core often reports this error 14/06/26 09:28:34. 917 html: Servlet error 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 java. nio. channels. channels. write (Channels. java: 60) at java. nio. channels. channels. access $000 (Channels. java: 47) at java. nio. channels. channels $1. write (Channels. java: 134) 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. for more information, see <G id = "1"> overview </G>. network. serverSocketReadHandler $ SafeRunnable. run (ServerSocketReadHandler. java: 260) at com. evermind. util. releasableResourcePooledExecutor $ MyWorker. run (ReleasableResourcePooledExecutor. java: 303) at java. lang. thread. run (Thread. java: 619)
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.
An error occurs when an application sends a message to the client and the client closes the connection. Basically, this is because the client suddenly ends the connection (for example, by closing the HTTP connection of the browser ). This error is generated when the user closes the Client Session and the server cannot write any information streams. If you open a link, click the second one before the page is rendered. The first request is suddenly canceled, and you will see this error. This is a normal behavior and you don't have to worry about it.