This content has been marked as final. Show 3 replies
These broke pipe exceptions happen when the client (browser) has closed the connection, but the server (your tag) continues to try to write to the stream.
This usually happens when someone clicks Back, Stop, etc. in the browser and it disconnects from the server before the request is finished. Sometimes, it can happen because, for example, the Content-Length header is incorrect (and the browser takes its value as true).
Usually, this is a non-event, and nothing to worry about. But if you are seeing them in your dev environment when you know you have not interrupted your browser, you might dig a bit more to find out why.
WLS server will try to filter these exceptions from the web container out of the log, since it is due to client (browser) action and we can't do anything about it. But the server doesn't catch all of them.
Thanks for the response.
I initially thought this exception was caused by clicking Back, Stop, etc. However, I found that by doing a browser interrupt, I actually get a "connection aborted by peer" exception and not the "broken pipe":
java.net.SocketException: socket write
error: Connection aborted by peer
This leads me to believe that the Broken pipe is caused by something else.
That infact is correct, as far as my understanding, the broken pipe exception occurs when the connection is closed by the client, yet the writing to the stream doesn't stop.
I am looking into this issue, and will get back to you on this with something concrete soon.