My Oracle Support Banner

Thread Blocked At {a} (Doc ID 1642588.1)

Last updated on MARCH 16, 2023

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.0 [Release 7.2]
Information in this document applies to any platform.
************Currency checked 3rd Jan 2019**********


During system performance testing, the customer observed a thread blocked at {a} during load injection. They also observed that the thread was not released until a restart of the application. The Customer executed two test scenarios which used different XMLs. This issue was observed in both test scenarios.

Error message :

"[STUCK] ExecuteThread: '44' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007fd739c5f800 nid=0x3ca2 waiting for monitor entry [0x0000000045a0f000]
  java.lang.Thread.State: BLOCKED (on object monitor)
  at Source)
  - waiting to lock (monitor:///) (a
  at oracle.communications.ordermanagement.orchestration.generation.w.a(Unknown Source)





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

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