Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: " Broken pipe" errors in log

Updated on May 7, 2019


Numerous " 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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us