Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of glen.vermeylen@gmail.com
 designates 66.249.82.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=PTkD89djTJ+IBzGesyCekUFgs1g+HtruFzNwCI8h/dxY++Hn/PkgduUfR2HrO/ZTF6a40eFOSbYFJXXoKmZX8ZLfTWC4exS3rM1gemVu1I8dgLah9mRUADhYwncaQPPH7PB98VHyN5nYJXlRx6e1yMIkjc12UQC5XYZFhFfulNQ=
Message-ID: <af3311880702210827n59599b7fj959c899f00f42599@mail.gmail.com>
Date: Wed, 21 Feb 2007 17:27:49 +0100
From: "Glen Vermeylen" <glen.vermeylen@gmail.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: Classloading deadlock in tomcat 5.5.20 / tomcat 6.0.9?
In-Reply-To: <45DC5C08.8010109@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_35706_18144045.1172075269455"
References: <af3311880702210210yb50552fqbf934e2534260ec@mail.gmail.com>
	 <af3311880702210317v961dc51xf0cd41c51bde66ca@mail.gmail.com>
	 <45DC5C08.8010109@apache.org>

------=_Part_35706_18144045.1172075269455
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thanks for the info.
We haven't had the problem again so far, so we will leave it as is (the
deadlock can should occur after a restart, so we can monitor it)
I may look into the fix on my development pc and let you know.

Glen.

2007/2/21, Remy Maucherat <remm@apache.org>:
>
> Glen Vermeylen wrote:
> > Hello all,
> >
> > We've seen strange behaviour on production (tomcat 5.5.20/java 6):
> > immediately after restart no-one could login. Using jconsole we saw tha=
t
> > there was a deadlock in the classloader.
> > Today I've also had the problem on development (tomcat 6.0.9/ java 6).
> > Its a
> > shame I was using tomcat 6.0.9 instead of 5.5.20, but it seems the two
> > problems are the same.
> > The problem occurs sometimes when multiple browsers are trying to
> > connect to
> > the server while it is still starting up.
> > I've tried to reproduce the problem on both 5.5.20 and 6.0.9 by trying
> to
> > start multiple browsers during application startup, but I cannot trigge=
r
> > the
> > deadlock again.
> > Using jconsole I saw there were 2 httpthreads locking eachother.
> >
> > Below are the stacktraces of both threads (I also have screenshots of
> > jconsole showing the threads the deadlocks-screen).
> >
> > I couldn't find the problem myself, so I turn to this list for help.
>
> Please test the patch if you can.
>
> R=E9my
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

------=_Part_35706_18144045.1172075269455--