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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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,

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.