Weblogic Tuxedo Connector (WTC) Stuck Threads Are Consuming CPU

(Doc ID 2010240.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


WLS/WTC with OSB 12.1.3 has stuck threads spinning on CPU.

All stuck threads have a similar thread dump stack trace to the following:

"[STUCK] ExecuteThread: '48' for queue: 'weblogic.kernel.Default
(self-tuning)'" Id=81 RUNNABLE
       at java.util.HashMap.transfer(HashMap.java:626)
       at java.util.HashMap.resize(HashMap.java:606)
       at java.util.HashMap.addEntry(HashMap.java:904)
       at java.util.HashMap.put(HashMap.java:530)
       at weblogic.wtc.jatmi.dsession._tpacall_internal(dsession.java:3072)
       at weblogic.wtc.jatmi.dsession.tprplycall(dsession.java:4870)
       at weblogic.wtc.gwt.TuxedoConnection.tpacall(TuxedoConnection.java:452)



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