Different ways to take the Threaddump:

In Solaris/Linux …etc Unix Based Boxes you need to findout the Servers Process ID…by running the following command from the Same box where the Server is running: 

Option 1: ps -ef | grep java qProcessbox 20650 1 0 Mar 26 ? 104:51 /opt/app/qProcessbox/java/jdk1.5.0_22/bin/java 

Option 2: Now use kill -3 20650 Syntax: kill -3 The OutPut of the Thread Dump will be generated in the Server STDOUT. 

Option 3. Simplest option to take Thread Dump is : Login to AdminConsole—>Server —> Monitoring —> Threads 

Option 4. Collecting Thread Dumps Using Jstack utility Open a Command or Shell prompt and then Move inside the \bin directory and then run the JStack.exe by passing the Process id of your Server Instance… Syntax: Jstack -l  

Option 5. Taking the JVM Details (Heap size and Jdk Details including OS details) including Thread Dump:
java weblogic.Admin -url t3://ServerHostName:7001 -username weblogic -password weblogic GET -pretty -type JVMRuntime
Weblogic Admin command to get the ServerRuntime status
java weblogic.Admin -url t3://ServerHostName:7001 -username weblogic -password weblogic GET -pretty -type ServerRuntime