Revision Orders Processing Time Is Longer, With Occasional Orchestration Cache Failures

(Doc ID 2032242.1)

Last updated on OCTOBER 02, 2017

Applies to:

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


Revision seems to be running slow with occasional errors related to Orchestration cache. Due to which sometimes the orders are stuck or it fails.



 Caused By: org.jboss.cache.lock.TimeoutException: read lock for /1006171/root/0/SystemInteractionManagement/67 could not be acquired by GlobalTransaction:<null>:146590 after 30000 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction:<null>:146620
, lock info: write owner=GlobalTransaction:<null>:146620 (org.jboss.cache.lock.LockStrategyReadCommitted@5fd1758c)
at org.jboss.cache.lock.IdentityLock.acquireReadLock(
at org.jboss.cache.Node.acquireReadLock(
at org.jboss.cache.Node.acquire(


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