There are many variables along the path to enlightenment. Don't give-up on Tomcat so soon.
Sometimes Tomcat is only as good as the applications deployed within her. Given that Tomcat has been up and running for me for as many as 90 days in a row with a high-use application accessing a database (of course, I write my own apps ;o), I would start with a code review of any custom applications within the beast before pointing to the beast itself. Honestly, I was just thinking this last night after my struggles with the default webdav servlet: "Is Tomcat a production ready reference j2se server or just a "finish it yourself" proof of concept toy?" Have you and I been separated at birth? I would stick with it, and cease development of new code until you have eliminated the existing installed code base as a source of the error. Look for connections that aren't being closed, for rampant object creation, for loitering objects, etc. Along the way, it would be helpful for you to beat up a separate, mirrored staging instance of your production environment using JMeter. Reproduce your problem with regularity by hitting each URL many times, then examining the results. If this type of application development was easy, we wouldn't all get paid the big bucks, right? Keep at it. Open source gets better if people like you and I continue to point out both the silver linings and the rain in any clouds that should form on the horizon. Bear Down. JCD -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak Sent: Tuesday, February 28, 2006 10:02 AM To: users@tomcat.apache.org Subject: Sad: Tomcat 5.5.x crashes almost every single day. Probably important: =================== - 2x Xeon, 3 GB mem - Linux 2.4.26 - Java 1.5.0_06-b05 - Apache Tomcat 5.5.15 - CATALINA_OPTS="\ -server \ -Djava.awt.headless=true \ -Dfile.encoding=UTF-8 \ -XX:MaxPermSize=256m \ -Xms1024m -Xmx1024m" - <Connector port="8009" protocol="AJP/1.3" maxThreads="200" minSpareThreads="25" maxSpareThreads="50" backlog="20" connectionTimeout="10000" enableLookups="true" redirectPort="8443" /> - mod_jk 1.2.15 - Apache Httpd 1.3.34 - 8 Tomcat vhosts - 8 webapps - each webapp runs on separate vhost - each webapp is Apache Cocoon 2.1.7 - system load avarage: usually under 0.5 - http load: not more then 20-30 concurrent req The pain: crashing Tomcat ====================== Everything works right until Tomcat suddenly crashes, what happens almost every single day. Sometimes it crashes with OOME / out of heap (heh, is 1GB not enought!?), but somtimes NOTHING wrong is logged into the logs - it just stops responding to requests (hangs). When Tomcat stops responding to requests JK eats all of 256 Apache HTTPd MaxClients so other httpd vhosts stop responding also. Disaster! Any ideas before abandoning Java technology? ;) Default Tomcat logging facility seems to be useless to me. j.u.l. logging.properties semantics looks like a programmers joke made to users (!). And even with swallowOutput it logs everything into catalina.out (?) I found none decent log4j-tomcat-virtual-hosts-logging-manual in Tomcat docs also. Is Tomcat a production ready reference j2se server or just a "finish it yourself" proof of concept toy? I've been crond-restarting Tomcat 4.1 on Java 1.4 every night for more than a year, and now I have to restart Tomcat 5.5.15 on Java 1.5 AND apache httpd also almost every single day. From my -user point of view, Tomcat doesn't change in a good direction. In fact in it is probably changing in wrong direction - at least the 4.1.x logger element has been working 'out of the box'. Come on! Am I the only one that has such problems with Tomcat? -- T. --------------------------------------------------------------------- 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]
