tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Romianowski" <antarap...@gmx.de>
Subject AW: LinkageError: duplicate Class definition
Date Wed, 05 Sep 2001 19:58:40 GMT
hi again,

i tried the nightly build 20010904 but nothing changed. tomorrow i will try
the latest build.

but thanks for your fast reply

pero

-----Ursprungliche Nachricht-----
Von: craigmcc@localhost [mailto:craigmcc@localhost]Im Auftrag von Craig
R. McClanahan
Gesendet: Mittwoch, 5. September 2001 20:38
An: Peter Romianowski
Cc: tomcat-dev@jakarta.apache.org
Betreff: Re: LinkageError: duplicate Class definition


There was a race condition in the web app class loader in 4.0-beta-7 that
could cause this.  Could you try it again with a recent nightly build.

NOTE:  Use the one from 20010906 (tonight) or 20010904 -- the one from
20010905 has a bug related to session cookies that I just fixed.

Craig


On Wed, 5 Sep 2001, Peter Romianowski wrote:

> Date: Wed, 5 Sep 2001 20:20:04 +0200
> From: Peter Romianowski <antarapero@gmx.de>
> Reply-To: tomcat-dev@jakarta.apache.org
> To: tomcat-dev@jakarta.apache.org
> Subject: LinkageError: duplicate Class definition
>
> 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.
>
> my configuration:
> 1 wep app (not war) with all required jars in WEB-INF/lib (which are
> deployed at startup)
>
> not btw but with full attention: tomcat rulez, man!
>
> sincerly,
> pero
>
>


Mime
View raw message