While I can appreciate the desire to never use Windows, that isn't reality in many of the industries that use our product, so running Tomcat on windows can't be considered an oddity or edge case. If it is, we better look for another app server.
With regard to finding a solution, I'll try the antiJarLocking setting, but I don't have any problem with any other JARS, so I don't hold out much hope for this fixing my problem. I may look at upgrading to JDK 7 - which has added a "close" method to the URLClassLoader. Perhaps this might fix it. If anyone else has any other ideas why ONLY JARs added via the addURL "hack" I've shown below don't get unloaded when the WEBAPP is shutdown - vs stopping Tomcat completely, I would greatly appreciate it. Thanks, Bob -----Original Message----- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Thursday, October 20, 2011 6:07 PM To: Tomcat Users List Subject: RE: JAR locked in Tomcat after using addUrl to dynamically add JAR to running webapp > From: Bob DeRemer [mailto:bob.dere...@thingworx.com] > Subject: RE: JAR locked in Tomcat after using addUrl to dynamically > add JAR to running webapp > I am not using a local app context and everything I've seen recommends > NOT using antijarlocking in production settings. Yes, except for the fact that you're doing rather odd things, including running on Windows... - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
