Write Lock Acquired From Root Node In Redo Mode (Doc ID 1519784.1)

Last updated on OCTOBER 18, 2016

Applies to:

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

Symptoms

User getting the following error when they tried to complete the order in redo mode.

 <ExecuteThread: '13' for queue: 'oms.automation'> <> com.mslv.oms.automation.AutomationException: failure upgrading lock: fqn=/446, caller=GlobalTransaction::1041, lock=read owners=[GlobalTransaction::1041, GlobalTransaction::1050, GlobalTransaction::1053, GlobalTransaction::1052], write owner=GlobalTransaction::1048 (org.jboss.cache.lock.LockStrategyReadCommitted@11f416e)
com.mslv.oms.automation.AutomationException: com.mslv.oms.automation.AutomationException: failure upgrading lock: fqn=/446, caller=GlobalTransaction::1041, lock=read owners=[GlobalTransaction::1041, GlobalTransaction::1050, GlobalTransaction::1053, GlobalTransaction::1052], write owner=GlobalTransaction::1048
(org.jboss.cache.lock.LockStrategyReadCommitted@11f416e)



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