My Oracle Support Banner

Stuck Thread Detection and Server Failure Detection Does Not Work (Doc ID 2150843.1)

Last updated on JULY 14, 2021

Applies to:

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

Symptoms

Detecting stuck thread by WebLogic does not behave correctly: When "StuckThreadCount" is exceeded,  "FailureAction" is not triggered.

1. Start WLS.
2. Login the admin console.
3. Move page.
DOMAIN_NAME > environment > server > SERVER_NAME > Configuration > Overload
3-1. Modify "MaxStuckThreadTime" 600 to 10.
3-2. Modify "StuckThreadCount" 0 to 1.
3-3. Modify "FailureAction", select "Force shutdown immediately".
3-3. Click the save button.
5. Deploy J01.war (index.jsp sleeps 600sec in J01.war)
6. Restart WLS.
7. Access http://hostname:port/J01/index.jsp only one connection.

"FailureAction" is not triggered even after 2 min.

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
References


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