Anything to keep the "Seattle Public Schools" off of .NET. ;-) This is probably less than helpful, but here goes: -- Most Solaris problems come from not installing the recommended O/S patches when installing the JVM (Sun takes the view: If my program doesn't work, patch the kernal :).
-- Your log files suggest that Tomcat isn't properly starting up. (i.e. Ajp13Interceptor isn't starting). This is usually a port conflict. You should check the stderr and/or the tomcat.log (if the default Logger goes there [not the out-of-box configuration]). It is almost certaintaily something on the Tomcat side (likely, a config problem). If you can post info on the Tomcat logs, then finding answers will be much easier. >WE have been using tomcat since 3.0 beta and very happy with it, but we >have a problem now with the connector mod_jk. We have been using 3.3 >but upgraded to 3.3.1 hoping to fix the problem (with no success). >After adding a new set of servlets to our (rather large) codebase we >swapped the jars holding the servlet code on each of our Sun Sparc >Solaris 7 servers and one Solaris * server. On all servers (fully >patched and running the latest jdk1.3 from sun) it went well except for >the one running Solaris 8 (everything else in the environment is >identical, though). After taking a few requests from Apache (1.3.x) >tomcat stops responding and our jk.log fills up with these messages >within a few seconds. If we switch back it works fine. >We can't find the source of the problem and were wondering if anyone >else recognizes this or knows anything that could help us. The Solaris >8 box is out of production until this is fixed. >Thanks for your help. >Paul >Unix System Admin/Webmaster >Seattle Public Schools -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
