Numerous "java.net.SocketException: Broken pipe" errors appear in the log files.
Such broken pipe error messages are commonly seen in the logs and have no functional or performance impact.
Broken pipes occur when Process Commander responds to a browser request, but the user closes the browser while while the response data is being sent..
Because the browser end of the connection is going away, the server receives and handles a broken pipe exception and reports this error in the log.
Users should be trained to explicitly log off and to wait for the log off display before closing the browser application.