My Oracle Support Banner

Order Component Does Not Start Due To Org.jboss.cache.lock.TimeoutException (Doc ID 2835079.1)

Last updated on FEBRUARY 08, 2024

Applies to:

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

Symptoms

Customer is using OACC and is experiencing the following timeouts in Orchestration Process:

"Caused By: org.jboss.cache.lock.TimeoutException: write lock for /1050641/orchestrationPlan/-1/-1/localOrderComponentByIndex/1634291997497 could not be acquired after 60000 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction::7612
 (caller=GlobalTransaction::7614, lock info: write owner=GlobalTransaction::7612 (org.jboss.cache.lock.LockStrategyReadCommitted@359e85cc))"


Also, in the order summary in the task UI, under the Dependencies tab they are observing the message "Order component of this order is blocked by [ Total x ]".

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.