WebLogic Stuck Threads In SOA 11g 11.1.1.7 Version
(Doc ID 2388629.1)
Last updated on AUGUST 30, 2023
Applies to:
JDBC - Version 11.2.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
WebLogic stuck threads in SOA 11g 11.1.1.7 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]
oracle.jdbc.driver.PhysicalConnection.isUsable(PhysicalConnection.java:19223)
oracle.jdbc.driver.LogicalConnection.isUsable(LogicalConnection.java:1976)
weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.isUsable(Unknown Source)
weblogic.jdbc.common.rac.internal.RACPooledConnectionStateImpl.isConnectionUsable(RACPooledConnectionStateImpl.java:224)
weblogic.jdbc.common.internal.HAConnectionEnv.test(HAConnectionEnv.java:52)
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |