Stuck Threads Due to JVM Lazy Unliocking Causes a Hang of Clustered Weblogic Managed Servers in ReplicatedSessionData (Doc ID 1470668.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle JRockit - Version R28 and later
Information in this document applies to any platform.

Symptoms

One can notice a lot of stuck threads with the following pattern:

[STUCK] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" id=484 idx=0x264 tid=29623 prio=1 alive, blocked, native_blocked, daemon
  -- Blocked trying to get lock: weblogic/servlet/internal/session/ReplicatedSessionData@0x1e6ed52d8[lazy unlocked]
  at jrockit/vm/Threads.sleep(I)V(Native Method)
  at jrockit/vm/Locks.waitForThinRelease(Locks.java:955)[optimized]
  at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1083)[optimized]

Cause

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