This content has been marked as final. Show 1 reply
Can you please check which WorkManager is used for this Stuck Thread? E.g. look in the Weblogic console >> Monitoring >> Threads (make sure Work Manager is added in the customization options) and identify which WorkManager this Thread belongs to. Then go in Work Manager Section and look at the Work Manager option: Ignore Stuck Threads.
We had the same problem in one of production environment e.g. a few stuck Threads (waiting forever from Web Service response) were causing Weblogic to throw 503 errors, health to change to WARNING etc. This is because Weblogic will take some action by default when STUCK Threads are present.
You can configure Weblogic to ignore Stuck Threads (by checking the Ignore Stuck Threads option) as often it does more harm than good unless the stuck Threads are involved in heavy computing tasks causing global impact like infinite looping, major Java Heap memory consumption etc.
My recommendation to you is as below:
- Perform your due diligence and double check if these Stuck Threads are not causing global impact on your JVM and server (Thread Dump analysis is key here)
- When assessment is completed, check the Ignore Stuck Threads option and see if it is helping your situation
- I also highly recommend that you work on the Stuck Thread problem itself e.g. please revisit the application code and add proper timeout (read/write & connection) with this Web Service in order to prevent Stuck Threads at the first place