I need to test WLST script that checks for stuck threads across some managed instances on a weblogic deployment. Unfortunately when I need to test, I am unable to get my stuck thread problem to rear its head. How can I intentionally create a stuck thread to test my script's detection with? My thoughts presently have been to sleep a thread for more than my stuck thread limit on Weblogic's settings, but that is also longer than the timeout for webpages. So my request should timeout before the thread ever becomes stuck. Apache commons executor is another idea... Does anyone have an elegant solution to reproducing this ugly issue?
First, you should never create threads in a JEE environment, it's forbidden by the specification. If your apps are doing this, you'll always have problems.
ReplyDeleteAnyway, a "stuck thread" is a little ambiguous. You can you put in into an infinite loop:
while(true){
try{
Thread.sleep(1000);
} catch (Exception e){
break;
}
}
or you could lock it on a monitor:
while (true){
new Object().wait();
}
If you want to have a stuck thread you can simply suspend it
ReplyDeletesynchronized(this){
wait();
}