My Oracle Support Banner

WebLogic Stuck Threads In SOA 11g Version (Doc ID 2388629.1)

Last updated on AUGUST 30, 2023

Applies to:

JDBC - Version and later
Information in this document applies to any platform.


WebLogic stuck threads in SOA 11g version .
Continuously receiving the below stuck threads due to which the Managed servers go into the warning state.

Below is the trace of the stuck thread:

#### <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[STUCK] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "633" seconds working on the request "Workmanager: weblogic.kernel.Default, Version: 0, Scheduled=false, Started=true, Started time: 633156 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-2376 "[STUCK] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {
  -- Blocked trying to get lock: oracle.jdbc.driver.T4CConnection@285d0fab[fat lock]
  weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.isUsable(Unknown Source)




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.