Wednesday, May 9, 2012

jvm freeze

The stack trace :
"[ACTIVE] ExecuteThread: for queue: 'weblogic.kernel.Default (self-tuning)'" id=16 idx=0x58 tid=* prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: netscape/ldap/LDAPSearchListener@0x0000000184932A78[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at jrockit/vm/Locks.wait([inlined]
at java/lang/Object.wait([optimized]
at netscape/ldap/LDAPMessageQueue.waitForMessage(
^-- Lock released while waiting: netscape/ldap/LDAPSearchListener@0x0000000184932A78[recursive]
at netscape/ldap/LDAPMessageQueue.waitFirstMessage(
^-- Lock released while waiting: netscape/ldap/LDAPSearchListener@0x0000000184932A78[fat lock]
at netscape/ldap/LDAPConnection.sendRequest(
^-- Holding lock: netscape/ldap/LDAPConnection@0x0000000184924B50[biased lock]
at netscape/ldap/ 

 The StackoverFlow issue observed is caused by a misconfiguration of LDAP server.

1. Open the console
2. through the menu Security realms->myRealm->Providers->Authenticaton->[provider]->Configuration->Provider Specific
3. Change the Group Membership Searching to limited
4. Change the Max Group Membership Search Level to 16
5. Save and restart WebLogic Server

1 comment:

Anonymous said...