Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A2788D5FE for ; Thu, 10 Jan 2013 11:17:10 +0000 (UTC) Received: (qmail 16058 invoked by uid 500); 10 Jan 2013 11:17:07 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 15550 invoked by uid 500); 10 Jan 2013 11:17:07 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 15522 invoked by uid 99); 10 Jan 2013 11:17:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 11:17:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of knst.kolinko@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 11:16:59 +0000 Received: by mail-vc0-f172.google.com with SMTP id fw7so383933vcb.3 for ; Thu, 10 Jan 2013 03:16:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=m1sZQdcIoqItVgos02MYA8SQ8ct8QTYfZh1fCjY9L4s=; b=ooLbgNmwcgayou0qjDK5uLaISnUHNwQtpHqnu9NCSaQHXYgLFA11oU1nPJ5FW0fayQ DIP/ku7UHzPJKAW1e56fophE1f20Ddl1vMok4eTo9+VDCxBaTKbaN48d1sOA21Fg8Wyq ps38WLMvDw849uT1+YDk+19SjzY+6O10K9ytGvVi0TW4zg+6APBlj7sF/Od+q4JY/RtS z7xcQF07wsjFZxq3UAFs+X3zi/0F1TJjD9bcTsdQQxhzYwey/D2KuHBy+Ud3wZyOjD2t W8NHSMvk1XvYV221OYyjSV9kYuq4ZunmGDI8qCoT9GDAwMowS3JtJ+08x2lWoktkJRqg AKHQ== MIME-Version: 1.0 Received: by 10.220.247.204 with SMTP id md12mr90874660vcb.27.1357816599033; Thu, 10 Jan 2013 03:16:39 -0800 (PST) Received: by 10.58.249.199 with HTTP; Thu, 10 Jan 2013 03:16:38 -0800 (PST) In-Reply-To: References: Date: Thu, 10 Jan 2013 15:16:38 +0400 Message-ID: Subject: Re: Tomcat AutoDeploy Interval (Delay / Frequency) From: Konstantin Kolinko To: Tomcat Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org 2013/1/10 Radek Szamrej : > Hi, > > I believe it's a generic Tomcat question: > > How can I configure / modify AutoDeploy interval (delay / frequency). > > It is taking too much time form WAR being copied until Tomcat recognizes it > and the application is redeployed / reinitialized. > > I would preferably like to reduce this delay to under 1 second. > > Tomcat 6.0.35; OS: Win7-64, JRE 1.6.x; > Autodeployment is performed by background thread of a Host. See its configuration reference if you want to tune its delays. By default it runs every 10 seconds. Instead of playing with the delays I'd suggest you to leverage either the Manager application or JMX. The Manager app protects the webapp that it uploads from being (auto)deployed too early and it triggers its deployment immediately upon upload, not relying on autodeploy. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org