TRIRIGA on Weblogic and the Broken Pipe messages
GiuCS 270003E2P0 Visits (8763)
Where to start? Well, let's take a look at the server.log and see how smoth the system is running...
2016-01-30 01:22:10,896 ERROR [com
tuning)') Report handled exception: com.
OMG, you see a lot of messages stating Broken Pipe! There is got to be something wrong, right?
Well, not necessarily...
These messages are rather usual in a TRIRIGA system served by Weblogic.
If not, there is no need to take action about those messages
If so, there are a few steps you can take to prevent performance degradation related (or even not) with those messages. Engage your DBA and ask for
AWR reports. That should give you a feel for where long-running queries or heavy page loading occurs.
For more performance tuning please refer to the Best Practices under this technote:
No need to say this does not occur in WebSphere