I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that we
are upgrading which I agree with for the features that it provides. But now
when I un-deploy it succeeds successfully but doesn't really undeploy there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?>
All combinations listed below have been tried
* <context antiJARLocking = "true">
* <context antiResourceLocking="true">
* <context antiJARLocking = "true" antiResourceLocking="true">
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
