Oracle Weblogic Server (MOSC)

MOSC Banner

UMS timer deadlock with LDAPConnThread

edited May 30, 2019 5:00AM in Oracle Weblogic Server (MOSC) 3 commentsAnswered

I have an issue in weblogic server version 12:2.1.2.0 running OSB 12c.

Found a Java-level deadlock:

Found one Java-level deadlock:
=============================
"UMS timer: [ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'":
  waiting to lock monitor (object 0x3b7c65d3, a netscape.ldap.LDAPConnThread),
  which is held by "LDAPConnThread-11141 ldaps://adldap.blue.local:389"
"LDAPConnThread-11141 ldaps://adldap.blue.local:389":
  waiting to lock monitor (object 0x48df0ad, a netscape.ldap.LDAPSearchListener),
  which is held by "UMS timer: [ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'"

Java stack information for the threads listed above:
===================================================
"UMS timer: [ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'":

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center