Oracel Weblogic application servers have stuck threads due to this thread "weblogic.work.SelfTuningWorkManagerImpl", the following error message is part of diganostic image logging.img.
Server: Oracle Weblogic Application Server 11g
<web:log-message>[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "655" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@5fe5d29", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Please help me in finding out why we are facing stuck threads in this self tuning work manager.
But from currently Stuck thread it seems that thread job is finished by 655 seconds.
This error is explicitly coming from weblogic. Weblogic will look for every 600 second to check whether any thread is running more than 600 Sec if it cross 600 sec then it will throw an error message on wls logging.
Now to avoid such thing increase Stuck max thread time out from 600 to 900 and monitor the logs again.
Thanks for your reply. But i have one more doubt. This is a production environment weblogic server, diagnostic image JVM.img. Weblogic thread count shows 414 , is this fair count? Or we need to tune some of our threads to reduce the numbers?