> From: André Warnier [mailto:[EMAIL PROTECTED] > Subject: Tomcat threads, II > > -classpath :/usr/lib/jvm/java-1.5.0-sun/jre//lib/jcert.jar: > /usr/lib/jvm/java-1.5.0-sun/jre//lib/jnet.jar: > /usr/lib/jvm/java-1.5.0-sun/jre//lib/jsse.jar: > /usr/share/tomcat5.5/bin/bootstrap.jar: > /usr/share/tomcat5.5/bin/commons-logging-api.jar
The classpath above is very wrong: no jars from jre/lib should *ever* be on the classpath. Those jars are already on the JVM's bootclasspath and will at best be ignored anywhere else. Their presence will at a minimum slow down Tomcat initialization. Also, the commons-logging-api.jar should not be on the classpath; Tomcat finds that all by itself, based on entries in the bootstrap.jar manifest. If you need commons-logging for a webapp, it should be in the webapp's WEB-INF/lib directory, not on classpath. Finally, the leading colon on the classpath shouldn't be there, but it appears to do little harm. > -Djava.security.manager Enabling the security manager slows things down; do you really need it? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
