> -----Original Message----- > From: Mayr Stefan [mailto:ste...@mayr-stefan.de] > Sent: Tuesday, May 14, 2013 5:17 AM > To: Tomcat Users List > Subject: RE: Delayed WAR expansion, timeout on context startup? > > Hi Chuck, > > Am Montag, den 13.05.2013, 15:44 +0200 schrieb "Caldarale, Charles R" > <chuck.caldar...@unisys.com>: > >> From: Stefan Mayr [mailto:ste...@mayr-stefan.de] > >> Subject: Delayed WAR expansion, timeout on context startup? > > > >> Are there any parameters to adjust deployment timeouts for these > >> contexts with large WAR files? > > > > Want to give us a hint about what Tomcat version, JVM level, and > > platform you're running on? It's rather difficult to answer _any_ > > question without the basics. > > Oh, that's a wonderful mix of applications and versions. Most common > are > > OS: SLES10 SP4, SLES11 SP2, both using TrendMicro ServerProtect 3 > Java: Java 6 U20,U33,U37,U45; Java 7 U09, U21 Tomcat 6.0.20, 6.0.35, > 6.0.35; 7.0.26, 7.0.27, 7.0.32 > > Developers are crying when we move applications to the newer os with > an active antivirus scanner. This affects all version combinations. > > The specific application failing is alfresco 4 running on Java 6 U33, > Tomcat 6.0.35 >
Sorry, this would have been a better reply to the OP, but here goes. Have you thought about adding the webapps directory to the anti-virus' list of ignored directories? I assume that the system(s) these WAR files are coming from also have anti-virus problems, but if they don't or are otherwise untrustworthy, modify your deployment procedure to first move the WAR file to a system/directory where it would be scanned, then move it from there to the production webapps directory. Jeff
