title: Thread dump of OC4J process link: https://onemoretech.wordpress.com/2010/09/20/thread-dump-of-oc4j-process/ author: lembobro description: post_id: 123 created: 2010/09/20 10:44:33 created_gmt: 2010/09/20 10:44:33 comment_status: open post_name: thread-dump-of-oc4j-process status: publish post_type: post

Thread dump of OC4J process

Let’s face it, J2EE app issues can be a real bear to diagnose. As a mere switch-thrower, someone who can bounce a container but is pretty much lost at the thread level, I recently needed to know how to take a thread dump of a running OC4J process for Greater Minds to ponder.

Here’s how it’s done:

1. Get the pid of the running OC4J process you’re interested in.

[oracle@apphost1 ~] opmnctl status -l
	
Processes in Instance: app_oas2.apphost1.example.com
--------------------+-------------------+-----------+-----------+--
ias-component       |  process-type     |  pid      |  status   |
--------------------+-------------------+-----------+-----------+--
OC4JGroup: APP_app  | OC4J:OC4J_app_app |   21034   |  Alive    |

2. Do a kill with the “-3” switch against that process.

[oracle@apphost1 ~] kill -3 21034

This will trigger a thread dump that will be recorded in the opmn log for that OC4J instance.

(e.g. /u01/app/oracle/product/oas2/opmn/logs/APP_appOC4J_app1.log)

Copyright 2004-2019 Phil Lembo