My Oracle Support Banner

OSM Notification Transformation Failed (Doc ID 2466641.1)

Last updated on APRIL 03, 2023

Applies to:

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

Symptoms

On : OSM 7.3.5.0.0 version.

ACTUAL BEHAVIOR
---------------
Some orders are failing  at creation level with the following  error:

Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: Error amending order [XXXXX] caused by:read lock for /XXXXX/root/0/NotifyReportingDB/XXXXX could not be acquired by GlobalTransaction::XXXXX after 15000 ms. Locks: Read lock owners: [] Write lock owner: GlobalTransaction::20479302 , lock info: write owner=GlobalTransaction::20479302 (org.jboss.cache.lock.LockStrategyReadCommitted@5fc31b90)

EXPECTED BEHAVIOR
-----------------------
Orders should get created

STEPS
-----------------------
Intermittent and happening in production

BUSINESS IMPACT
-----------------------
orders are not getting created

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References


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