Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 7696 invoked from network); 22 Aug 2008 18:00:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2008 18:00:41 -0000 Received: (qmail 66087 invoked by uid 500); 22 Aug 2008 18:00:23 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 66068 invoked by uid 500); 22 Aug 2008 18:00:23 -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 66054 invoked by uid 99); 22 Aug 2008 18:00:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 11:00:23 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 17:59:24 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KWavR-0003a2-4S for users@tomcat.apache.org; Fri, 22 Aug 2008 10:59:53 -0700 Message-ID: <19112602.post@talk.nabble.com> Date: Fri, 22 Aug 2008 10:59:53 -0700 (PDT) From: edponce To: users@tomcat.apache.org Subject: Re: HOW TO install/setup 2 instances of tomcat on same server In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: edponce@appslm.com References: <19079289.post@talk.nabble.com> <48AC9F0F.9060207@ice-sa.com> <48ACA35C.4050003@ice-sa.com> X-Virus-Checked: Checked by ClamAV on apache.org Thank you Tom, I think the other repliers were going to far on what they wanted to do. this exactly why i want 2 different sessions, "It can also b= e useful for evaluating a new =20 version before you unleash it to production." so if i understood everything i just need to duplicate the tomcat folder, do i need to rename it or something? Then "On the duplicated tomcat =20 directory, you need to edit the server.xml file so that the second =20 server.xml as unique ports for the shutdown port, the interface port =20 (eg 8080 could become 8081 etc)" and how can i check if i've done this correctly? that both instances are running? Thanks for your help... a little more info on what I am running Server version: Apache Tomcat/5.5.20 Server built: May 15 2007 09:00:46 Server number: 5.5.20.0 OS Name: Linux OS Version: 2.6.22.14-72.fc6 Architecture: i386 JVM Version: 1.4.2 JVM Vendor: Free Software Foundation, Inc. Thomas Haines-2 wrote: >=20 >> >>> edponce wrote: >>>> I know this question has been asked a lot but I've read different =20 >>>> solutions >>>> depending on the needs of the problem. I need to have 2 instances =20 >>>> of tomcat >>>> on the same server for the same application. One would be for =20 >>>> production and >>>> the other for development (which can be start and stopped whenever =20 >>>> without >>>> affecting the production one). >>>>> From my understanding i need to have each instance on different =20 >>>>> ports and >>>> modifying some other files but what I am missing is the technical =20 >>>> things. >>>> Can any one please guide me on the correct direction so that i =20 >>>> don't mess up >>>> anything! I've never worked with Tomcat that is why i have no idea =20 >>>> on how to >>>> do it. >>> Andr=C3=A9 Warnier wrote: >> >> You do not necessarily need two separate instances of Tomcat. [...] =20 >> There also exists the possibility to run one Tomcat with different =20 >> "Virtual Hosts", on the same port 80. >> Each one of these virtual hosts would have a different "DNS =20 >> name" (like "realserver.mycompany.com" and =20 >> "testserver.mycompany.com") and could have a different directory =20 >> where the applications reside, but the application itself would be =20 >> named the same way. >> >> The difference between the above solutions and two really separate =20 >> Tomcat instances would be if the test application could really crash =20 >> the whole server, in which case you may not like one of the above =20 >> solutions. >> >> Comments anyone ? >=20 > When I was new to tomcat (arguably when compared with some members of =20 > this list, I could still be considered new), I found it conceptually =20 > easier to work with two instances, as you don't need to switch context = =20 > names etc when you want to deploy live. Whilst a little cumbersome, =20 > and inefficient from a resource usage standpoint, when you're =20 > learning, being able to restart tomcat as you shop and change the =20 > server.xml file etc can be useful, without fear of breaking the =20 > production service. It can also be useful for evaluating a new =20 > version before you unleash it to production. >=20 > edponce: If you want to run two instances, the easiest way, to my =20 > mind, is to duplicate the tomcat directory. On the duplicated tomcat =20 > directory, you need to edit the server.xml file so that the second =20 > server.xml as unique ports for the shutdown port, the interface port =20 > (eg 8080 could become 8081 etc). Once you have made these changes, =20 > you should be able to start each of them up by running their =20 > respective startup scripts. >=20 > You could achieve the same using links and a few other sharing =20 > techniques, but for simplicity's sake, I think this approach to two =20 > instances using duplicated directories is the most robust. >=20 > Tom >=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/HOW-TO-install-setup-2-= instances-of-tomcat-on-same-server-tp19079289p19112602.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org