Oracle WebLogic: Managed Server 1: OSMServer1 Is Failed State
(Doc ID 2849051.1)
Last updated on AUGUST 11, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.3.5.0.0 and laterInformation in this document applies to any platform.
Symptoms
Managed Server fails intermittently
deadlocked thread] [ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)':
---------------------------------------------------------------------------------------------------
Thread '[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'' is waiting to acquire lock 'java.util.ArrayList@791db7ab' that is held by thread '[ACTIVE] ExecuteThread: '58' for queue: 'weblogic.kernel.Default (self-tuning)''
Stack trace:
------------
oracle.communications.ordermanagement.scheduler.GenericTimerSupport.setTimer(GenericTimerSupport.java:268)
oracle.communications.ordermanagement.scheduler.SchedulerEJBBean.ejbTimeout(SchedulerEJBBean.java:218)
sun.reflect.GeneratedMethodAccessor1465.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
.........
Reason: Thread deadlock detected>
Reason: Thread deadlock detected>
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 |
| Cause |
| Solution |
| References |