• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3053
  • Last Modified:

high CPU utilization Weblogic thread / process


Understood we need to start some sort of admin console on Weblogic or WAS & then
issue "kill -3 pid_of_process"   : trying to do this for high CPU Weblogic process.

Can someone provide or point me to a link & possibly explain how to analyze the
thread dumps.

Does EE allow us to post thread dumps & someone would analyze it?
3 Solutions
1. I hope you would have already nailed down that WLS is the process taking lot of CPU time.
2. Once #1 is validated, and if you are not able to run profiler, take threaddumps at regular intervals.
3. Check if you have lots of threads in RUNNABLE states. And it would give the stacktrace as well. Check if you can observe the pattern.

Best would be to simulate this behavior on test bed and run java profiler to naildown CPU issues.
sunhuxAuthor Commented:

> simulate this behavior on test bed and run java profiler to naildown CPU issues

Would be good if you can elaborate how to simulate this & how to use the java
profiler;  possibly can point me to some links that have this information
Ramakanta SahooCommented:
For creating heapdump with windows service follow bellow steps:

Add below details to the existing JAVA_OPTS cmdline used to start weblogic managed server/in Java arguments just after the xms xmx values like below

-server -Xms2048m -Xmx4096m -XX:MaxPermSize=256m -XX:+PrintGCDetails -Xloggc:D:\GcStats\gc.log -XX:+HeapDumpOnOutOfMemoryError -classpath "D:\SOFTWA ~1\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;......................

Note: Do not change any existing parameters only add -XX:+PrintGCDetails -Xloggc:D:\GcStats\gc.log -XX:+HeapDumpOnOutOfMemoryError   to get all gc status and dump files.

To create ThreadDumps on demand follow below steps:
1. login to shell
2.Navigate to WL_HOME\common\bin  directory start “wlst.sh” file.
3.Once WLST is connected in offline mode execute below command to make it online with managed server.
connect(‘<AdminUserName>’, ‘<AdminUserPassWord>’, ‘t3:://<WL_HOST_NAME>:<MS_PORT>’)
connect('weblogic', 'weblogic', 't3://mysystem:7006')

4.      Once You are Online with Managed Server Run below command to get Stack Trace if any present.If you get stack trace then copy paste it into a text file and keep it.

5.      Put below command to get all the running variables available.Copy paste all variables to a text file and save it

6.      Put below command to get Full Java Thread Dump in a dump file.

7.      ThreadDump command will produce a dump file like Thread_Dump_<ManagedServerName>.txt in the current WL_HOME\common\bin folder.This txt file will contain all info about Java Threads at that point of time

To Analyse Heapdump see below url:


Best Regards,
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now