- You can configure max stuck thread timeout in WebLogic admin console
- When you get an alert or observe high CPU, do a top or prstat command
- #2 will identify high cpu consuming java processes
- Convert the PID to hex to get thread number
- Do a thread dump (using kill -3 or admin console or jstack) and identify the thread
- 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:
Post a Comment