Automation Stops In Amending/Redo Mode After Trying To Obtain A Write Lock 10 Times (Doc ID 1534107.1)

Last updated on DECEMBER 01, 2014

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.

Symptoms

An automation at a certain task stops in Amending/Redo mode.


In the log file, ExecuteThread '9' tried to obtain a lock 10 times:
 lock.ReadWriteLockWithUpgrade: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock>
 jboss.JBossOrderCacheManager: Could not obtain write lock to cache fqn[/1209] This thread will sleep for 1000ms and then try again.>
No log for the thread was recorded afterward (we wait more than 30 minutes), probably it failed to obtain a lock.

The problem is Timeout Exception or other Exception can not be found in the log file.
We expected that Timeout Exception should be raised after the failure so that it triggers an external retry by oms_events queue.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms