Well, in this case, adding the Jar in setclasspath.sh, including it in /tomcat/lib, and not having it in WEB-INF/lib doesn't make any difference. So even if we load this second Jar (in addition to the first jar that helped with the initial issue), through setclasspath.sh we are still seeing this error.
-Suresh -----Original Message----- From: Caldarale, Charles R [mailto:[email protected]] Sent: Friday, June 26, 2009 2:14 PM To: Tomcat Users List Subject: RE: Tomcat 6.0 and JULI issue. > From: Kodichath, Suresh [mailto:[email protected]] > Subject: RE: Tomcat 6.0 and JULI issue. > > Just want to add the Jar for this class file is at > webapps/WEB-INF/lib/. Is this jar file also in Tomcat's startup classpath (as Mark suggested)? If so, you must remove it from WEB-INF/lib, since you must never have the same class in two places in a given branch of the classloader tree. - 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 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]
