[Php-java-bridge-users] Orphaned httpd's

[Abbett, J. <Jon...@ch...>]

On one of our machines, we run a web application with a Tomcat server
and a PHP site that uses the PHP-Java Bridge.  Twice, the Tomcat
application has caused the mod_jk.log file to exceed two gigabytes,
essentially bringing down Tomcat and Apache.

Once we shutdown Tomcat and cleared the log file, we tried to restart
Apache, which failed:

[root@pingsvr root]# service httpd start
starting httpd: (98)Address already in use: make_sock: could not bind to
address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs


We then looked for a process that was bound to port 80:

# ps auxw|grep httpd
root     27852  0.0  0.0 13288 2916 ?        S    Nov20   0:00
/u1/apache2/bin/httpd -k start -DSSL

# netstat -pan|grep ":80"
tcp     0    0 0.0.0.0:8000       0.0.0.0:*        LISTEN
32104/java         =20
tcp     0    0 127.0.0.1:8005     0.0.0.0:*        LISTEN
32104/java         =20
tcp     0    0 0.0.0.0:8009       0.0.0.0:*        LISTEN
32104/java         =20
tcp     0    0 0.0.0.0:8080       0.0.0.0:*        LISTEN
32104/java         =20
tcp     0    0 0.0.0.0:80         0.0.0.0:*        LISTEN
27853/java =20


You'll see that process 27853 is bound to port 80, and its parent is
"java".  Our sysadmin insists that Tomcat doesn't bind to port 80 in our
setup and that "php-java-bridge constantly causes this orphaned httpd
problem when restarting apache."

Is there anything we can do on our side to alleviate this problem? Is
there some improvement to the php-java-bridge that's necessary?


Thanks!
Jon Abbett