On 24/02/2010 09:36, Taylan Develioglu wrote:
I thought I'd add the connector definitions too, :<Connector port="80" protocol="org.apache.coyote.http11.Http11AprProtocol" compression="1024" keepAliveTimeout="60000" maxKeepAliveRequests="-1" enableLookups="false" redirectPort="443" maxThreads="150" pollerSize="32768" pollerThreadCount="4"/> <Connector port="443" protocol="org.apache.coyote.http11.Http11AprProtocol" SSLEnabled="true" enableLookups="false" maxThreads="10" scheme="https" secure="true" SSLCertificateFile="/etc/ssl/private/something.crt" SSLCertificateKeyFile="/etc/ssl/private/something.key" SSLCACertificateFile="/etc/ssl/certs/ca.crt"/> On Wed, 2010-02-24 at 10:23 +0100, Taylan Develioglu wrote:Hi, I have jvm's, running tomcat and our application, exiting mysteriously, and was wondering if anyone could give me some advice on how to debug this thing. There is nothing in catalina.out, nor our application logs, and no hotspot error file. GC log looks normal. No trace in system logs. I am left completely clueless :(, has anyone dealt with a problem like this before? Any help appreciated. - Tomcat 6.0.24 - TC native 1.1.18 - APR 1.3.9 - Sun JDK 6u18 - Debian Lenny, 2.6.31.10-amd64 2 servlets, one as ROOT. 2 HTTP connectors that use TCNative/APR. JAVA_OPTS ( ): -verbose:gc -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -Dfile.encoding=UTF-8 -Djava.io.tmpdir=$TMP_DIR -Djava.library.path=/usr/local/lib -Djava.endorsed.dirs=$CATALINA_BASE/endorsed -Dcatalina.base=$CATALINA_BASE -Dcatalina.home=$CATALINA_HOME -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file="$CATALINA_BASE/conf/logging.properties" -XX:+PrintGCDetails -Xloggc:$CATALINA_BASE/logs/gc.log -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70 -Xms$JAVA_HEAP_SIZE -Xmx$JAVA_HEAP_SIZE -XX:NewSize=$JAVA_EDEN_SIZE -XX:MaxNewSize=$JAVA_EDEN_SIZE -XX:PermSize=$JAVA_PERM_SIZE -XX:MaxPermSize=$JAVA_PERM_SIZE -Xss$JAVA_STCK_SIZE -XX:+UseLargePages
There's no actual heap size settings in the above. But you get a couple of points for trying.
Google "Linux Out Of Memory killer" or "OOM Killer" and then check the server logs carefully. (e.g. /var/log/messages)
p
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
