{"id":8144,"date":"2015-07-03T05:33:45","date_gmt":"2015-07-03T09:33:45","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=8144"},"modified":"2015-07-03T05:33:45","modified_gmt":"2015-07-03T09:33:45","slug":"weblogic-server-fmw-generating-thread-dumps-using-os-commands","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2015\/07\/03\/weblogic-server-fmw-generating-thread-dumps-using-os-commands\/","title":{"rendered":"WebLogic Server (FMW) : Generating Thread Dumps using OS commands"},"content":{"rendered":"

This post is coming from our Oracle Fusion Middleware Training<\/a>\u00a0where we cover Oracle WebLogic Server<\/strong> on Day1 . One of the performance issue that commonly encountered in poorly written application (or on not so performant Fusion Middleware infrastructure) is Stuck Threads<\/strong>.<\/p>\n

Stuck Threads<\/strong> in WebLogic Server means a thread performing the same request for a very long time and more than the configurable Stuck Thread Max Time in WebLogic .<\/p>\n

Thread dumps<\/strong> are diagnosis information that is used to analyse and troubleshoot performance related issues such as server hangs, deadlocks, slow running, idle or stuck applications etc.<\/p>\n

How to generate Thread dumps?<\/strong>
\nIn this post, I will walk you through the steps to generate Thread dumps of a server using operating system<\/strong> (O.S.) commands.<\/p>\n

1.<\/strong> Start the server from command line script (using nohup). Let us take managed server as an example for which we need to\u00a0generate the thread dumps so start the server using script as shown below.
\ncd $DOMAIN_HOME\/bin
\nnohup .\/startManagedWeblogic.sh <Server_name> &<\/strong><\/p>\n

2.<\/strong> Now identify the PID<\/strong> (java Process ID) for the managed server using the below command:
\nps auxwww | grep \u2013i java | grep \u2013i <server_name> (This command is for Solaris)<\/p>\n

3.<\/strong> Now run the below command to create the thread dump.
\nkill -3 <PID><\/p>\n

(This will send a signal to the process whose dump we require. This signal causes the Java Virtual Machine to generate a stack trace of the process.<\/span>)<\/p>\n

This command will create thread dump in the nohup.out<\/strong> file (where we started the managed server)<\/p>\n

4. Open the nohup.out<\/strong> file to see generated thread dumps:<\/p>\n

References<\/strong><\/span><\/p>\n