On the Linux box we use for testing, we have a Tomcat 4.1.12 instance that controls two custom webapps and a manager app. The Tomcat process starts up fine when I use startup.sh, generating some 35 "java ... start" processes in my ps list. However, when I attempt to stop the Tomcat process with shutdown.sh, about 10 of the java processes do not die, particularly the parent process. I must find the parent process and kill it specifically to completely stop the Tomcat.
The 10 processes are identified as running when I look for them with ps -r. I can run startup.sh again while they remain on the ps list and a new Tomcat instance is started. Unhappily, if I do this too often, I use up all the processes on the box. We have a second Tomcat 4.1.12 instance on the same Linux box that responds to shutdown.sh perfectly. Has anybody an idea of why this is happening and how I can fix it before we move the application into production? Thanks. Athens Group Experience. Technology. Results. ----------------------------------------------- John McNeill Athens Group Inc. 5608 Parkcrest Dr., Ste. 200 Austin, TX 78731 Voice: 512.345.0600, ext. 135 Fax: 512.345.4088 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Web: <http://www.athensgroup.com/> http://www.athensgroup.com
