one thing to consider is that Thread dumps are redirected to server standard out. So if you're under unix environment and take the thread dump with kill -3 [PID] command you need to have redirected the standard out to a file. This usually is done using the nohup command while starting the server.
If you have nodemangaer starting your servers the standart out is redirected to $DOMAIN_HOME/servers/$SERVER_NAME/logs/$SERVER_NAME.out
Hi Joe Thanks for info I have been through this also.
But this wont work as the Wl server is not running and Managed server is through windows service only.
open the console and click on the server(s) that has the stuck threads. click the monitoring tab and click on performance tab in the monitoring tab. then click dump thread stacks
Amit this also wont work as there is no admin server or node manager to monitor.
Kill -3 is for unix env.
One more easy step is in UNIX env. 1.5 JDK and in WINDOWS 1.6 JDK
run below commands to get thread dump.( All needs to be running in command line only else you wont get any PID)
jps -l (Java process list)
jstack -l PID (This will give you total thread dump)
Its not applicable for me too as its windows env., 1.5 JDK and only Managed server is running and that to in service mode only.
The problem is only Managed Server is running and its only as service.
I got a good solution to this... just posting for future reference of users.
Start wlst.cmd tool
It will be in offline mode
connect to the managed server and make it online.
this will create a file named Thread_Dump_<ManagedServerName>.txt in local directory.
Thats all get the file and check it out. Full Dump any time.