Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of pills@hmcrecord.ch designates
 84.16.68.89 as permitted sender)
Message-ID: <47B54EE5.1040301@hmcrecord.ch>
Date: Fri, 15 Feb 2008 09:35:49 +0100
From: =?ISO-8859-1?Q?S=E9bastien_Piller?= <pills@hmcrecord.ch>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Undeployment problem
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hello,

yes, I don't know what is Thread-1. Maybe a Wicket thread (on my side, I 
don't start any thread anywhere). As I'm investigating more on that, I'm 
now quite sure it's a wicket issue and not a tomcat one.

antiResourceLocking="true" on the context.xml do the trick, but I don't 
know if I can use it in my production environnement...

Caldarale, Charles R a �crit :
> >From the stack trace, it looks like Thread-1 is the one waiting for the
> shutdown command, but the shutdown script didn't seem to be able to
> connect to it.  Odd that it's called "Thread-1" - it's just "main" in
> current 5.5 and 6.0 levels.
>
>  - Chuck

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org