Oracle iAS - OC4J process "stop"'ped

From: Lyall Barbour <>
Date: Fri, 11 Sep 2009 09:14:01 -0500
Message-Id: <>

Anyone ever seen this, where the iAS server console status is up and running and a status on opmnctl, the HTTP_Server is "Alive" but the OC4J process is "Stop" and the pid is the pid of another process running? opmnctl status
Processes in Instance:
ias-component      | process-type       |     pid | status

LogLoader          | logloaderd         |     N/A | Down
dcm-daemon         | dcm-daemon         |     N/A | Down
OC4J               | home               |   30867 | Alive
HTTP_Server        | HTTP_Server        |   30868 | Alive DSA                | DSA                |     N/A | Down

i fixed the problem, but wanted to know if anybody has seen this, so that i can have it NOT happen again. The status of OC4J was Stop and the pid was 2047 which was the same pid as the xinetd process running. I tried to stopall and wait, then startall, but OC4J really wanted to use 2047 pid. So, i logged in as root and killall xinetd, logged oracle and opmnctl stopall, waited, then did xinetd -stayalive -pidfile /var/run/, which is what is in our rc3.d script when the server boots. Xinetd didn't use 2047 anymore, but used: ps -eaf|grep xinetd

oracle     591   356  0 10:13 pts/2    00:00:00 grep xinetd
root     30802     1  0 09:51 ?        00:00:00 xinetd -stayalive -pidfile /var/run/

and, of course, the new opmnctl startall has OC4J using what's above.

Anyone seen that?



An Excellent Credit Score is 750
See Yours in Just 2 Easy Steps!

-- Received on Fri Sep 11 2009 - 09:14:01 CDT

Original text of this message