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
> From: Oleg Lyashko [mailto:[EMAIL PROTECTED]
> Subject: Re: Undeployment problem
>
> What is your "Thread-1"?
>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
connec
Hi Sébastien,
What is your "Thread-1"? It is not a daemon, if not terminated "manually",
it will continue to run after "main" thread stop.
Regards,
Oleg
On Thu, Feb 14, 2008 at 5:02 PM, Sébastien Piller <[EMAIL PROTECTED]>
wrote:
> Hello guys,
>
> I have a little problem with Tomcat. I have an
