(1) Install TC as many times as you need JVM instances;
(2) for each instance, rename home before proceeding with another
installation eg. 
CATALINA_HOME_tc1=/path/to/tc1
CATALINA_HOME_tc2=/path/to/tc2
etc
(3) for each inctance rename respective startup scripts eg
startup_tc1.sh or catalina_tc1.sh
startup_tc2.sh 
etc
(4) modify workers.properties to include the loadbalancer worker eg
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_worker=myTC1, myTC2, myTC3,...
etc
(5) go through your configuratioo fles to ensure consisency in re-naming
worker to "loadbalancer"
(6) should you need to tie a vhost to a specific JVM or box then instead
of "loadbalancer", use a worker eg "myTC1"
eg.
(httpd.conf)
<VirtualHost 192.16.100.10:80>
  ServerName dodgy.programmer.com.hk
  ...
  JkMount /goodClass loadbalancer
  JkMount /goodClass/* loadbalancer
  JkMount /dodgyClass myTC1
  JkMount /DodgyClass/* myTC1 
</VirtualHost>
(7) In server.xml, ensure you have the corresponding virtual host and
docbase
(8) In web.xml, likewise ensure you have the corresponding mappings.

Yoav, John, tomcat-people, if this is correct, do you need someone to
write a "howto" ?



"Pitre, Russell" wrote:
> 
> Hey people......
> 
> Where can i find more information on the web about this subject,
> specifically setting up multiple jvm's tied to it's respective tomcat
> installation?  Doesn't have to include multiple processors....
> 
> I'm very interested in this subject, basically, just curious as to how
> it all works  :)
> 
> Thanx in advance!
> Russ
> 
> -----Original Message-----
> From: John Turner [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 4:16 PM
> To: Tomcat Users List
> Subject: Re: Tomcat and multiple processors
> 
> Matt Raible wrote:
> 
> > 1.  Does it support multiple processors?  We have a Tomcat instance in
> 
> > production on a NT box with 4 processors, but Tomcat only seems to use
> 
> > one. Does the 1.4.2 JVM support MP?
> 
> Yes, at least on Sun hardware with Solaris 8, and Intel hardware with RH
> Linux 7.x (duals only...we don't have quads).  Don't know about Windows.
> 
> > 2.  We have IIS on the front end, and we are currently not able to
> > migrate to Apache.  We'd like to use the connectors (jk or jk2) to do
> > load-balancing and failover.  Do these connectors provide the support
> > we need?  Should be use a clustering architecture like JavaSpaces
> > (http://www.onjava.com/lpt/a/2422) instead?
> 
> The connectors can load balance, but unfortunately the IIS versions are
> sort of a crapshoot in my mind.
> 
> > 3.  We plan on deploying 42+ applications to a number of Tomcat
> > servers. Since each application will support 1 customer - I think it's
> 
> > a good idea to have 1 app -> 1 tomcat - so if Tomcat crashes, it only
> > affects that customer
> > - rather than all customers.  I've heard of setting up a CATALINA_BASE
> to
> > share Tomcat's core files, and then setup webapps directories for each
> > customer.  Does this sound reasonable?  Have have others done
> something like
> > this?
> 
> I agree with Yoav. All the way back with Tomcat 3.1 we had ours setup
> this way:
> 
> 1 virtual host = 1 Tomcat instance = 1 VM = 1 application
> 
> We've had a couple dozen set up like this for a long time, works like a
> charm.  I prefer this over using CATALINA_BASE, as I can treat each
> virtual host separately from any other, including giving each different
> JVM memory settings, etc.  Admittedly, we're an ASP, so we can dictate
> how many web apps go with each virtual host, but I would think having
> completely separate Tomcat instances would make sense in most real
> production environments.  The only thing you "lose" with multiple Tomcat
> instances is disk space, and disk is cheap.
> 
> John
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to