Friday, February 20, 2009

Finding out what Weblogic processes is running in Unix

if you are using NodeManager, it will most likely be running on port 5556


netstat -putanuw | grep 555

will give you this:

tcp 0 0 :::5556 :::* LISTEN 32092/java


where 32092 is the NodeManager's PID

ps -ef | grep 32092

will give you:

beasvbd 10921 22827 0 13:53 pts/0 00:00:00 grep 32092
beasvbd 11121 32092 0 Feb13 ? 00:03:31 /opt/bea/jrockit/R27.3.1/bin/java blablabla weblogic.Server
beasvbd 32092 32069 0 Feb13 ? 00:00:23 /opt/bea/jrockit/R27.3.1/bin/java blablabla weblogic.NodeManager



note that the weblogic.Server's parent PID is the NodeManager's PID


32069 is the shell's PID, which was used to start the server


Note that a Weblogic instance can have multiple Network channels:

[beasvbd@bcdev05 bea_install]$ netstat -putanuw | grep 5610
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 ::ffff:127.0.0.1:5610 :::* LISTEN 29082/java
tcp 0 0 ::ffff:10.40.16.109:5610 :::* LISTEN 29082/java
tcp 0 0 ::ffff:10.40.20.109:5610 :::* LISTEN 29082/java


each of them corresponds to a different Network Interface. note that the PID is the same.

No comments: