Which jars are locked? There was an issue like this with log4j. I can't remember the exact reason, but it was fixed with the 1.2.8 release. Anything that grabs hangs onto resources is going to be an issue. In the case of Struts, I'd make sure you don't have commons-logging stuff in WEB-INF/lib. Put it in common/lib if it isn't already there.
Jake
At 11:05 AM 6/3/2003 +1000, you wrote:
All,
I have some problems using the undeploy/deploy manager web app commands
to perform their tasks. Basically it seems that resources are still left open,
in particular jar files in my app's WEB-INF/lib directory are kept locked
and so are not removed from the file system upon calls to remove/undeploy
using ant tasks.
I've searched through the archives but I see no reference to this problem. I'm obviously looking in the wrong place...
This is a problem for me since I'm trying to automate the redeployment cycle during development. The only solution I found so far was to stop Tomcat altogether and restart it, which kind of defeats the purpose of using the Manager app in the first place.
My setup: Tomcat 4.1.12 running as a service on Windows XP, A web app using struts.
Any help would be appreciated.
Cheers,
Bonny
CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Siemens Ltd., ABN 98004347880, or Siemens (NZ) Limited immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
