When Predecessor Order and Successor Order is Owned by Two Different Node. a Dead Lock Happen when Creating the Successor Order (Doc ID 1556691.1)

Last updated on SEPTEMBER 22, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 to 7.2.2 [Release 7.0.0 to 7.2.2]
Information in this document applies to any platform.

Symptoms

On : 7.0.3 version

ACTUAL BEHAVIOR
---------------
Getting Time Out error after the OSM patch upgrade while processing the Orders.

“Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: encountered error starting orchestration caused by:Timeout while attempting to release order[XXXX] from local server[osm_msXX] after 200 seconds. “

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