OCI : APM Java Agent Is Generating Stuck Threads On Managed Servers
(Doc ID 2965829.1)
Last updated on AUGUST 04, 2023
Applies to:
OCI Application Performance Monitoring Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
In Oracle Cloud Infrastructure (OCI), APM Java Agent is monitoring the Managed Servers and Stuck Threads are reported in the Managed Server logs.
Managed Server out file had the following STUCK thread stack:
<Jul 18, 2023 5:40:24,187 AM CST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '176' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "631" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@cab3e0d[POST /BNCR/BNCR_OSB_ObtenerClientesMonederoId_v2 ECID-Context: <ECID-Context>
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in
[STUCK] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" #71 daemon prio=1 os_prio=0 tid=<TID> waiting on condition [0x00007f8fd60df000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
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 |
Cause |
Solution |