Oracle Identity Governance (OIG): Unlock or Password Change Requests Generating Stuck or Hogging Threads due to Object Locks on tcServerProperties class (Doc ID 2882799.1)

Last updated on JULY 20, 2022

Applies to:

Symptoms

Users executing password changes or unlock actions have noted significant performance degradation.  This action usually takes 10-30 seconds, and is now taking 3-5 minutes.  The WLS Console shows some threads hogging resources.  Thread dumps of the Oracle Identity Manager (OIM) server show that the underlying threads associated with the these requests are holding a lock on the object tcServerProperties with each of the threads requiring (and waiting for) that same object.  This may only be visible when the number of password changes or unlocks increases so that there are multiple occurring at the same time. 

The thread dump of the thread holding the lock looks like this:

You can use the sample script from Note 2801604.1 to generate a series of thread dumps at measured intervals.  If you do this, you will see that none of the threads hold the object lock for very long, so the threads are not technically stuck, just slow.  When we ran the script on an OIM server with a 15 second interval, the same thread never held tcServerProperties for more than 20 seconds.  However, all of the threads are waiting for that object and cannot proceed without it.  This means that all of the threads are bottlenecked into a line waiting to get access (10-30 seconds per thread), so a single thread might wait more than a minute just for this one action.

Changes

None 

Cause

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