AnsweredAssumed Answered

Process Engine Response 'Sluggish' After 13.2 Upgrade

Question asked by Robert Ensinger on Dec 17, 2013
Latest reply on Dec 19, 2013 by Robert Ensinger

Hi all. How does one troubleshoot a 'sluggish' background engine?

We recently upgraded to 13.2 fixpack 4. Since our upgrade our users are having issue with the responsiveness of 'data management' processes such as a checkbox we use to copy the previous week's status reports and a few other 'attribute setter' processes. They've been trained that the process engine isn't like an API call, that there *is* some processing time, but usually they give it a beat, click refresh and get their expected results. Post our 13.2 upgrade, the response time on these process that usually took seconds is now minutes.

Previous to the upgrade we deleted all completed process instances. As you can see it's not sweating and there isn't a deluge of completed processes (every quarter we purge the quarter before last to retain, in effect, a least a running quarter of history).

While troubleshooting, I 'opened up' the pipelines to the max possible in hopes that this would help. So far this has not.

JVM Paremeters are -Xms2048m -Xmx3072m -XX:MaxPermSize=192m -XX:-UseGCOverheadLimit.   Message Time To Live is 120, Message Reciever Interval is 1, Exception Run Interval is Normal.

This is a dedicated process engine server. As you can see it doesn't appear to be overburdened.

Any experience with an issue like this or tips & best practices for configuring, troubleshooting and maintaining the process engine is greatly appreciated.

Outcomes