Hi, When I started my project, Tomcat 5.5.15 was the current Tomcat version, so naturally I chose that as a jumping off point. I've managed to shoehorn our collection of servlets and code into an Apache + mod_jk + Tomcat environment, and it works beautifully with Tomcat 5.5.15. Since 5.5.16 and 5.5.17 beta had been released, it seemed like a good idea to try those with my configuration, and have had nothing but headaches, including:
- Tomcat takes significantly longer to start up, and opens many more files while doing so, requiring an increase in the open files ulimit. 5.5.15 takes ~7secs to start -- 5.5.16+ takes between 35 and 45 seconds. - JSPs only work in the root of my webapp, regardless of how I configure the web.xml or my JkMounts in Apache, and if they're placed anywhere else, I get a Tomcat 404 error page (the blue and white one), in spite of having working 404 page definitions in Apache and Tomcat. Mostly I am doing JSP includes of servlet URLs and have enabled the crossContext attribute in my configuration. I can elaborate on this if necessary. - a servlet using the Barbecue barcode package now magically crashes the JVM and Tomcat, leaving a hs_errPID.log. This servlet is currently in production and is stable and performant on another servlet container, and runs even better on the 5.5.15 setup. 5.5.17 beta exhibits all of the same issues as 5.5.16. 5.5.12 works just as great as 5.5.15. I'm running CentOS 4.3, Java 1.5.0_06, Apache 1.3.34, mod_jk 1.2.15. Is there any big change that occured between 5.5.15 and 5.5.16 with regard to EL that I'm missing? Any, and I mean any help appreciated. Corey --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
