Hi, You must look at your java code in order to find any function that are "deprecated". Sometimes this functions are the problem of memory leaks, high cpu usage, etc...
Best regards, Abraham Fernández Álvarez Dpto. de Informática FNAC ESPAÑA S.A. Parque Empresarial La Finca Pº de la Finca, bloque 11 2ª Planta 28223 Pozuelo de Alarcón (Madrid) ( +34 91 7689211 7 +34 91 7689225 / [EMAIL PROTECTED] : http://www.fnac.es -----Mensaje original----- De: news [mailto:[EMAIL PROTECTED] En nombre de Tomasz Nowak Enviado el: martes, 28 de febrero de 2006 18:02 Para: users@tomcat.apache.org Asunto: 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]
