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 3530DE0A4 for ; Thu, 7 Feb 2013 19:30:50 +0000 (UTC) Received: (qmail 57271 invoked by uid 500); 7 Feb 2013 19:30:46 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 57191 invoked by uid 500); 7 Feb 2013 19:30:46 -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 57182 invoked by uid 99); 7 Feb 2013 19:30:46 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 19:30:46 +0000 Received: from localhost (HELO [192.168.23.9]) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 19:30:46 +0000 Message-ID: <511400DF.5090407@apache.org> Date: Thu, 07 Feb 2013 19:30:39 +0000 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: problem with context.xml for parallel deployments References: In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 07/02/2013 19:17, Zippy Zeppoli wrote: > I've been testing out parallel deployments > (http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment) > in my tomcat cluster. It seems to work really well if I futz around > with naming the filenames. > > Here's what works: > 1) cp /artifacts/someapp##001.war /tmp/war-listener > --- app gets deployed to the farm by farmdeployer successfully > 2) cp /artifacts/someapp##002.war /tmp/war-listener > --- someapp##002.war gets deployed, new sessions are migrated over to > this version of the application, context path remains the same for > both > --- someapp##001.war still receives connections, but is undeployed > (manually set in server.xml) as sessions expire > --- eventually someapp##002.war is the only app serving requests and deployed > > All good. However, I was trying to use context.xml to define the > version, but this fails, the cluster just hangs and never deploys the > app. > > Here was an example of a META-INF/context.xml I was using: > > > > What was I doing wrong with this method? Failing to read the documentation. Do you see the "name" attribute for a Context defined anywhere in this list: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Attributes > Is it a best practice to version just using the filename, both? Again, read the docs: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Naming > Thanks for any insights, the documentation doesn't seem to explain > this very well and there isn't a resource on the web that goes over > this in detail. Looks pretty clear to me. Then I did write it. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org