I have seen numerous postings about sig 11 problems with few remedies so here is one I
hope helps someone. We put together a huge matrix of Java, Tomcat, Apache and OS
parameters and finally worked around a jdk bug.
Under fairly heavy load (7-8 transactions/s) we were getting sig 11s with the Sun JDK
1.4.2_02. We weren't getting much in the way of stack traces to try to track down the
problem so we switched to IBM JDK 1.4.1. We ended up having to turn JIT optimzation
off like this in the tomcat startup.
export JITC_COMPILEOPT=NALL{org/apache/tomcat/util/buf/Ascii}{parseInt}
also did extensive analysis of garbage collection with these two entries in JAVA_OPTS
-Xgcpolicy:optavgpause -verbosegc
first one seems similar to Sun's conncurrent gc - 2nd one for logging each gc
One thing which helped us find it was cranking the ConnectionTimeout down to 1s in the
Tomcat server.xml.
We will probably revist the Sun jdk at some point.
-Dave
________________________________
David E. Muller
Configuration Manager
Overture Services, Inc.
www.overture.com
Office: 760.476.6406
Mobile: 760.458.2714
