I opened a Bug at https://issues.apache.org/bugzilla/show_bug.cgi?id=56051
I will give disabling automatic deployment a try and comment on the bug if that changes things. We are experimenting as well with just skipping the whole Cluster/FarmWarDeployer thing completely and just deploying through manager/curl on all nodes, as the application is stateless anyways. Thanks for your help! -----Ursprüngliche Nachricht----- Von: Mark Thomas [mailto:ma...@apache.org] Gesendet: Mittwoch, 22. Januar 2014 13:12 An: Tomcat Users List Betreff: Re: FarmWarDeployer ocassionally fails with "Application is being serviced" On 22/01/2014 10:24, Michael Gloegl wrote: > Can somebody shed any light here on what the "serviced" status means and how > we can avoid this FarmWarDeployer Failure? It usually means that the manager application or the auto deployment code is doing something (starting, stopping, deploying, undeploying etc) the web application. The Javadoc looks like it could do with some fixes. Looking at the docs and the code, the problem is that the FarmWarDeployer writes the WAR to the appBase and then marks it is serviced. This means that the auto deployment code may get there first which confuses the FarmWarDeployer. I'd say this is a bug in the FarmWarDeployer. Please open a Bugzilla entry. As a work-around, you should be able to disable automatic deployment (untested). Thanks, Mark --------------------------------------------------------------------- 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
