My Oracle Support Banner

Multiple Execute Threads Devoted to One Transaction Abandonment (Doc ID 2398585.1)

Last updated on MAY 17, 2018

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

 

Thread dump shows that hundreds of execute threads are blocked at Weblogic Server transaction abandon activity. The stack trace pattern is as below sample.

"[ACTIVE] ExecuteThread: '373' for queue: 'weblogic.kernel.Default (self-tuning)'" #590 daemon prio=5 os_prio=0 tid=0x00007ff9e1434000 nid=0x736f waiting for monitor entry [0x00007ff925d5c000]

java.lang.Thread.State: BLOCKED (on object monitor)

at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:1113)

- waiting to lock <0x0000000490804f60> (a weblogic.transaction.internal.ServerSCInfo)

at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:3191)

at weblogic.transaction.internal.ServerTransactionImpl.abandonNow(ServerTransactionImpl.java:3605)

at weblogic.transaction.internal.ServerTransactionImpl.access$300(ServerTransactionImpl.java:60)

at weblogic.transaction.internal.ServerTransactionImpl$3.run(ServerTransactionImpl.java:3587)

at weblogic.transaction.internal.PlatformHelperImpl$3.run(PlatformHelperImpl.java:1103)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

Locked ownable synchronizers:

- None

 

 

Changes

 

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!


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