Imagine that you are in your company’s IT department. No users are complaining about TRIRIGA for weeks, and you decide to do some preventive work. Where to start? Well, let’s take a look at the server.log and see how smooth the system is running:
2016-01-30 01:22: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]
OMG, you see a lot of messages stating “Broken pipe”! There has got to be something wrong, right? Well, not necessarily. These messages are rather typical in a TRIRIGA system served by WebLogic. The first question you need to raise is: Is there a problem being observed in the front-end, especially related to performance degradation? If not, there is no need to take action about those messages.
But if yes, there are a few steps you can take to prevent performance degradation, related (or even not related) to those messages. Engage your DBA and ask for Automatic Workload Repository (AWR) reports. That should give you a feel for where long-running queries or heavy page loading occurs. No need to say it, but this does not occur in WebSphere.
[Admin: This post is related to the 02.07.16 post about “broken pipe” exceptions in the server.log.]