Friday, November 21, 2014

High CPU and/or stuck thread diagnosis

  1. You can configure max stuck thread timeout in WebLogic admin console
  2. When you get an alert or observe high CPU, do a top or prstat command
  3. #2 will identify high cpu consuming java processes
  4. Convert the PID to hex to get thread number
  5. Do a thread dump (using kill -3 or admin console or jstack) and identify the thread
  6. Look at where it is stuck or processing
http://middlewaremagic.com/weblogic/?tag=stuck-thread
http://www.munzandmore.com/2012/ora/weblogic-stuck-threads-howto

No comments: