Hot deploying with tomcat on windows now works if I sent "antiResourceLocking" to true in my context.xml : http://tomcat.apache.org/tomcat-5.5-doc/config/context.html if I don't set that and copy in a new war file the old one isn't fully removed, leaving only the 2 wicket jars in my WEB-INF/lib directory.
What antiResourceLocking does: If true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur. If not specified, the default value is false. Unfortunately I can't tell from JMX / thread dumps what is causing the file locking (if indeed that is the problem). Chris cwilkes wrote: > > Yep, that gets past FileCleaner's reaper thread not being shut down. > Should I create a JIRA entry for this? I only see the destroy() method > called in the WebApplication.internalDestroy() method so it is probably > safe to do. > > I'm on to another problem with Tomcat (5.5.23 on Windows) still hanging > after that change. I don't see a wic > -- View this message in context: http://www.nabble.com/Does-FileCleaner.destroy-stop-the-reaper-thread--tf4342035.html#a12375374 Sent from the Wicket - Dev mailing list archive at Nabble.com.
