We experieced the issue last week.But we did not collect the thread dumps and restarted the server.
Now the issue does not seem to recur testing it with increasing load.
Please help us with steps to reproduce the same so that we can loo at fixing of the same.
Cheers,
Phunsuk Wangdu
Joseph Antoine Raja
Greenhorn
Joined: Feb 01, 2010
Posts: 29
posted
0
As you mentioned the stress of the application load might be exceeded – this might be the crash point
Mitesh Lashkari
Greenhorn
Joined: Feb 04, 2010
Posts: 9
posted
0
Hi,
In Weblogic a thread is treated as 'Stuck' if it is continiously working for a defined time period. Server keeps monitoring each thread and check after a certain period of a time if thread is running and then compare it with "Stuck thread max time" attribute.
This situation can be managed by altering following two attributes
1) Stuck thread max time.
2) Stuck thread time interval.
You can decrease "Stuck thread max time" to reproduce the scenario.
This would help you in generating the scenario but obviously not under exact circumstances which you had earlier.
Hope this would help.
Regards
Mitesh
subject: Regarding Thread pool stuck and servers getting overloaded