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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
