Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 62566 invoked by uid 500); 6 Sep 2001 01:55:46 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 62557 invoked from network); 6 Sep 2001 01:55:45 -0000 Message-ID: <006a01c13677$8290a450$82deb018@intalio.com> From: "Remy Maucherat" To: References: Subject: Re: LinkageError: duplicate Class definition Date: Wed, 5 Sep 2001 18:59:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > hi there, > > I got a weird problem getting on here. I'm using tomcat 4b07 on both win2000 > and linux. > after startup I start some threads and when they execute for the first time > I get a LinkageError: duplicate Class definition. > there are 4 things with this I dont understand: > 1st: all classes are there exactly once. no jar is twice within the > classpath (I checked that a dozen times) > 2nd: the error occurs only when the thread is executing for the very first > time. after each execution I wait some amount of time (Thread.sleep) and > when the code which crashed before is re-executed everything works fine. > 3rd: the linkage error is not restricted to a particular package. if I > remove the non working threads, then the linkage error comes back again at > some other place/thread. > 4th: sometimes (very rarely) the error does not occur, but after restarting > tomcat it is back again. > > i figured out that this is not nescessarely related to threads I start. if i > do not start any thread of my own, then the first jsp-execution (after > compilation) brings up the error. At least the JSP part is supposed to be fixed. It's bug 3107 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3107), and the attached test case (which looks like it would duplicate your problem) is now working fine for me. If it's still not working, would it be possible to pull together a test case ? Could I get the stack trace you get in your threaded app if pulling together a test case isn't possible ? > my configuration: > 1 wep app (not war) with all required jars in WEB-INF/lib (which are > deployed at startup) Remy