Lock Contention in com.bea.wli.sb.service.ServiceImpl.getRuntimeEffectiveWSDL() after GC (Doc ID 2320182.1)

Last updated on MAY 16, 2023

Applies to:

Oracle Service Bus - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

Performance issues due to lock contention on com.bea.wli.sb.service.ServiceImpl.getRuntimeEffectiveWSDL(). Thread dumps are showing many threads waiting for same lock:

[ACTIVE] ExecuteThread: '32' for queue: 'weblogic.kernel.Default (self-tuning)'" id=167 idx=0x288 tid=54272 prio=5 alive, blocked, native_blocked, daemon
  -- Blocked trying to get lock: java/lang/Object@0x88f9b860[fat lock]
  at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)
  at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1411)[optimized]
  at jrockit/vm/Locks.lockFat(Locks.java:1512)[optimized]
  at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1054)[optimized]
  at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1005)[optimized]
  at com/bea/wli/sb/service/ServiceImpl.getRuntimeEffectiveWSDL(ServiceImpl.java:578)[inlined]
  at com/bea/wli/sb/service/ServiceImpl.getEffectiveWSPolicy(ServiceImpl.java:397)[optimized]

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

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

Lock Contention in com.bea.wli.sb.service.ServiceImpl.getRuntimeEffectiveWSDL() after GC (Doc ID 2320182.1)

Applies to:

Symptoms

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!