Weblogic Thread Dumps

example:

add the following to the weblogic startup and restart the Managed Server:

-Dweblogic.Stderr="instancename.stderr.log"

java -cp /usr/bea/jdk131_06/lib/tools.jar:/usr/bea/weblogic700/server:/usr/bea/weblogic700/server/lib/weblogic_sp.jar:/usr/bea/weblogic700/server/lib/weblogic.jar:${CLASSPATH}" weblogic.Admin -url server:8089 -username weblogic -password weblogic THREAD_DUMP

look in "instancename.stderr.log" file to see the thread dump

On RedHat 8:

Modified startup script with bold entries :

$JAVA_HOME/bin/java -classpath "$CLASSPATH" $JAVA_VM $ManagedMemory $JavaOptions -verbose:gc -Dweblogic.Name=$ManagedName -Dweblogic.management.username=$WLUSER -Dweblogic.management.password=$WLPASSWORD -Dweblogic.management.server=$AdminURL -Djava.security.policy=$WLPOL weblogic.Server >> $LOGFILE.weblogic.log 2>&1 &

Restarted the managed server.

Ran:

ps -efHl --cols 5000 |grep "I put the value for weblogic.Name here to find my managed server"

i.e.

ps -efHl --cols 5000 |grep 'internetapp:<port>'

Make note of the PID

Ran:

kill -3 <pid>

Open your $LOGFILE.weblogic.log file to view the thread dump. In my case $LOGFILE is defined in the startup so it maps to the managed servers name.

Drag and drop log into samurai tool

http://yusuke.homeip.net/samurai/?english#content_1_0

No comments: