Even After Selecting Ignore Stuck Thread in Work Manager, WebLogic Server Goes to Warning State
(Doc ID 1496788.1)
Last updated on NOVEMBER 18, 2024
Applies to:
Oracle WebLogic Server - Version 10.3 and laterInformation in this document applies to any platform.
Symptoms
The application has a resource adapter which does continuous polling. This thread was getting stuck, and as a result the server was going to critical state and shutting down.
To avoid this behavior, a work manager has been created with a min and max thread constraint. As a result, the server shutdown is avoided but the server status still changes to warning and sometimes critical state due to the stuck thread. Hence, the ignore stuck thread option for that work manager was checked. That is done by navigating in the administration console to Environment -> Work Managers -> select the work manager, and after that select the option ignore stuck threads. However, even after that change the server still goes to a warning or critical state.
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 |