mvn tomcat:deploy "Cannot invoke Tomcat manager"

[yqu]

Hi,

Once you cleaned it up, can you try

1) run tomcat:deploy for the first deployment.
2) run tomcat:redeploy for the following deployments.

Do you still get same issue?

Yong

[gbags]

Hi,

Once you cleaned it up, can you try

1) run tomcat:deploy for the first deployment.
2) run tomcat:redeploy for the following deployments.

Do you still get same issue?

Yong

Yong, I am having the same issues. What appears to be happening is tomcat is locking on all the libraries in the community folder. If you attempt to undeploy the app, it removes everything except the lib folder due to file locks. stopping the webapp does not remove these file locks. The only way around this that I have figured is to re-start tomcat, undeploy community and redeploy.

I do not know if this is a OS depenedent issue as I am running on Windows 7 and don't have the time currently to investigate other operating systems.

I am also running as Tomcat 6 (latest) as a windows service on windows 7

edit....
Additionally, because of these file locks, after the first deploy, redeploy and undeploy do not work correctly.

[yqu]

Hi,

I am using Windows XP and Tomcat 6.0.20. The redeploy works fine.

Yong

[michael.waluk]

I have the exact same issue on XP with tomcat 6.0.20. This only happens when I use spring-tomcat-weaver.jar to do the load-time-weaving of Aspectj aspects. gbags is probably weaving and yqu is probably not.

That weaver was the only one that I could get working reliably. It could be that the others (using a -javaagent) work the first time but not after a redeploy. If anyone knows how to get redeploy working again, please comment.

[jepal]

Hi,
I have the same problem. I have LDAP security in the realm of the server.xml.
When trying to build with the maven, it is looking for the default user authentication (admin/"") for the manager application and fails.
Any help?