When looking at the server.log file from TRIRIGA, the system administrator can observe Broken Pipe errors. How those errors impact the system and what they mean?
No symptoms are observed in the system front-end.
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
Diagnosing The Problem
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]
Resolving The Problem
There is no known resolution to this problem. It is recommended that the system administrator engage the DBA and, on Oracle, ask for 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 TRIRIGA Best Practices for System Performance paper and ensure that all have been followed to optimize performance.
17 June 2018