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.
subject: Regarding Thread pool stuck and servers getting overloaded