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 I hoped for something generic like, e.g. set -Dorg.catalina.deploy.timeoutX=... In the meantime, look here: http://wiki.apache.org/tomcat/HowTo/FasterStartUp - Chuck Hardly a chance to change anything. Mostly vendor applications like alfresco, jira, confluence, ... We have to take them as is. We know the source of the problem (av scanner, NOT tomcat) but need to wait for the vendor. Sometimes (alfresco case) we close our eyes and stop the scanner until the application is deployed. Thanks, Stefan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Delayed WAR expansion, timeout on context startup?
On 14/05/2013 11:17, Mayr Stefan wrote: I hoped for something generic like, e.g. set -Dorg.catalina.deploy.timeoutX=... There is no such configuration setting because there is no such feature. Tomcat will wait for as long as it takes for an application to start. There are no timeouts. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Delayed WAR expansion, timeout on context startup?
Hi Mark, Am Dienstag, den 14.05.2013, 12:21 +0200 schrieb Mark Thomas ma...@apache.org: On 14/05/2013 11:17, Mayr Stefan wrote: I hoped for something generic like, e.g. set -Dorg.catalina.deploy.timeoutX=... There is no such configuration setting because there is no such feature. Tomcat will wait for as long as it takes for an application to start. There are no timeouts. Sigh, I feared this answer. So we need to dig deeper what else in alfresco causes the failure. Thank you Stefan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Delayed WAR expansion, timeout on context startup?
On Tue, May 14, 2013 at 12:17:10PM +0200, Mayr Stefan wrote: 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. Aside: [wearing my *developer* hat] if developers are seriously affected by moving to a newer version of infrastructure, we need to learn to write less-brittle code. This should not be a big deal. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature
RE: Delayed WAR expansion, timeout on context startup?
-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
Re: Delayed WAR expansion, timeout on context startup?
Am 14.05.2013 16:13, schrieb Jeffrey Janner: -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 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Yes we did but hundreds of tomcats with different applications on different servers and enterprise procedures for changing this settings ... Wrong list for this type of problem :-) Thanks, Stefan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Delayed WAR expansion, timeout on context startup?
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. In the meantime, look here: http://wiki.apache.org/tomcat/HowTo/FasterStartUp - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
