Honestly, I have no idea how to even start debugging this. :-( In all likelyhood, SOMETHING is holding onto something from the cxf jar. Possibly a InputStream from a schema in the jar or one of the xml files in the jar or similar. However, I have NO clue how to debug that. :-(
I don't know if one of the memory analyzers could get a list of InputStreams or other objects. If you have one of those, debugging with that may be a good idea. Alternatively, switch to a real OS that doesn't have the problem, like Linux. :-) Dan On Wednesday 24 September 2008 7:30:33 am Antonio Leonforte wrote: > Thank you for the suggestions. We were not cleaning up properly the > temporary folder where we create our WAR file, so that old CXF file was > there for this reason but was not the cause of the problem. In fact, the > problem still exists with the other file (cxf-2.1.2.jar), which still > prevents Tomcat from completely undeploying the web app. > > We have found on > (http://wiki.metawerx.net/wiki/TroubleshootingApplicationDeploymentOnTomcat >) a reference to an antiJARLocking="true" to be set in the Context (ie: in > the context.xml file or server.xml file) during development. We'll try this > out and then report. Any other hint would be much appreciated. > > dkulp wrote: > > First question: > >> cxf-2.0.5-incubator > >> cxf-2.1.2 > > > > Why is there two versions of cxf there? That's definitely asking for > > problems. > > > > Dan -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
