Which platform/OS? I've no experience on Win, but I never experienced a tomcat crash on unix/linux. Nevertheless five comments:
0) jk2 is no longer under development. The only active connector development for apache is mod_jk and mod_proxy (for the upcoming apache 2.1/2.2). 1) If you really want to use clustering, either choose the tomcat 5.5 line (preferably with fastasyncmode), or at least 5.0.28 (better 5.0.30). 2) Some *nixes and shells will send signals, when the user starting tomcat logs out of the system resulting in killed tomcat processes. Inj that case use nohup or any similar workaround. 3) With replication you will need more memory. Any indications for OutOfMemory? 4) The only real process crashes I experienced where fixed by updates to bug fix releases of the JVM. > I am trying to set up a 2-node cluster. Each node runs 5.0.24 with apache > 2.0.50 in front (with SSL). I use the JK2 v. 2.0.43 connector. > > What I'm seeing doesn't make sense. I get tomcat and apache up on the > first node and everything works fine. The clustering section in the > server.xml file is uncommented and I've configured all of the appropriate > values. Once that's working I turn to node 2. On the second node I start > apache and tomcat and everything looks good for a bit. I have most of the > tomcat output going to the consoleappender so I capture that output into a > file. After anywhere from 1 - 2 minutes tomcat exits. There is no thread > dump printed in any of the logfiles (including stdout/stderr). When I > look > in my log files I see normal activity for the little bit that TC is > running > and then it simply quits. There is no indication of TC going through the > shutdown process. > > When tomcat exits it generates a non-zero exit code. When I first saw > this > problem a few weeks ago it was when I was deploying clustering in my > production environment. After seeing TC exit like this 3 times in a row I > rolled back my deployment and have spent the time trying to figure out > what > went wrong. I didn't note the exit code number! I have two different > test > environments setup with very similar configuration and I'm not having this > problem on either of them. > > I'm at the point now where I'm going to have to try to deploy to > production > again but since I've not changed anything I'm fully expecting it to > fail. This time I'll note the exit code number. > > Have any of you seen anything like this? What things can I adjust to > enable more debugging output? > > Thanks for any info. > > -Mike Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
