[OO Tip] Central process can use 100% of CPU for no reason
Using Operations Orchestration (OO) Central, the process has more than 25% CPU usage in the system, even though a flow execution or Central login is established.
This issue can happen after an established and consistent Central install has been running. Once it occurs, the CPU maintains a high usage level and never returns to normal.
After examination of the approximate time in the Central_wrapper.log, when the problem starts, no validate cause can be determined.
The reason for this issue is that a loop in the Jetty Secure Socket Layer (SSL) handler would wait indefinitely for a response which would never come. To correct this issue an updated jetty-sslengine jar is needed.
Direct link to the document below:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.