High CPU Usage When Searching For Employee Name on Compensation Workbench (CWB) Allocation Page (Doc ID 2477122.1)

Last updated on MAY 06, 2019

Applies to:

Symptoms

Actual Observation:

When using the Name Search field on CWB Allocation Page, and searching for a search string that does not exist,
The page locks up and you have to kill the session to recover.
When you review in UNIX (by using the 'TOP' command on the application server), you see the process_id showing as 99% usage, which does not fluctuate, or terminate.

If the issue is hit a second time (using the search name function again), the CPU Usage jumps to 198%, and 'stair-steps' like this each time the issue is hit again.
Eventually the JVM memory will be bogged down and force an undesirable JVM Bounce to resolve the issue.

Expected Results:

We expect CWB functionality to work with out consuming high CPU.

Steps to Reproduce:

1. Go to responsibility Compensation Workbench for Administrators.
2. Click into an Allocation task for a given plan.
     - In the Name Search field (above the Allocation Table), enter a search string like *xcv* or another non-existent search string surrounded by wildcard characters.
        Instead of returning a message that the search string doesn't exist - the page locks up and forces the user to terminate the session.
3. Using PUTTY, mount the applications server, and enter the command 'TOP'.
If the issue has occurred - the top line will be a static 99% or so and never change, while the other processes jump around and fluctuate in CPU Usage.
If the search page is wildcard-searched a second time, the CPU usage will 'stair-step' another 99% or so to around 198%, and again remain static.
CPU Usage is only able to be terminated when the JVM is bounced, and that is not a real possibility in a production environment.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.