What does the “broken pipe” exception mean in the server.log?


When looking at the TRIRIGA server.log file, the system administrator can observe “broken pipe” exception errors. How do those errors impact the system and what do they mean?

No symptoms are observed in the system front end. But this can be caused when a user calls a page, but then closes the session prior to the page loading. It can also be an indicator of poor performance. This is observed in Linux environments running WebLogic. For example, look for the server.log entry:

2016-01-11 01:32:10,896 ERROR [com.tririga.platform.error.ErrorHandler]([ACTIVE] ExecuteThread: ‘4’ for queue: ‘weblogic.kernel.Default (self-tuning)’) Report handled exception: com.tririga.platform.error.PlatformRuntimeException: java.io.IOException: Broken pipe[MID-1070145274]

There is no known resolution to this problem. It is recommended that the system administrator engage the DBA and, on Oracle, ask for Automatic Workload Repository (AWR) reports. That should give you a feel for where long-running queries or heavy page loading occurs. It is also recommended that the system administrator review the IBM TRIRIGA Best Practices for System Performance [PDF] document and ensure that everything has been followed to optimize performance.

Continue reading

One thought on “What does the “broken pipe” exception mean in the server.log?

  1. Pingback: Getting “broken pipe” messages with TRIRIGA on WebLogic | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.