RE: Multipe Tomcat instances
OK. I understand the separation point. I think as long as I can start separate instances by referencing a separate server.xml file, I'll do it that way. If I need to upgrade one web app, then I can split it out then. Thanks for the input. It's appreciated. -- On Wed, 2004-12-01 at 09:05, Shapira, Yoav wrote: > Hi, > Both Tim's and QM's approaches are viable, and I use them as well under > certain circumstances. But by default I just have completely separate > Tomcat installations. The only things they might share are the > hardware, OS, and JDK, depending on the requirements. So while the > CATALINA_BASE splitting is possible, I don't actually do it in practice. > > The motivation for me is complete separation, so that if one application > requires a Tomcat upgrade it can be done separately from others. But > then again I'm somewhat of a fanatic when it comes to webapp > self-containment. (Although it's served me well). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multipe Tomcat instances
Hi, Both Tim's and QM's approaches are viable, and I use them as well under certain circumstances. But by default I just have completely separate Tomcat installations. The only things they might share are the hardware, OS, and JDK, depending on the requirements. So while the CATALINA_BASE splitting is possible, I don't actually do it in practice. The motivation for me is complete separation, so that if one application requires a Tomcat upgrade it can be done separately from others. But then again I'm somewhat of a fanatic when it comes to webapp self-containment. (Although it's served me well). Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Tim Funk [mailto:[EMAIL PROTECTED] >Sent: Wednesday, December 01, 2004 7:22 AM >To: Tomcat Users List >Subject: Re: Multipe Tomcat instances > >If you run tomcat in a cluster where all the webapps are identical, we use >the exact same (copy) of server.xml for all the tomcat instances. So when >one >server.xml is changed - we copy it to all of the tomcat installations. > >Then we rely on variable substitution in server.xml for items which might >need to be specific such as ip addresses, port numbers, and worker names. > >We never call startup.sh directly - we have wrapper scripts which set the >appropriate -D variables for us. > >-Tim > >Ryan Daly wrote: > >> On Mon, 2004-11-29 at 14:53, Shapira, Yoav wrote: >> >>>Hi, >>>I do it this way all the time. The biggest pro is complete separation. >>>If one app gets whacky (heavy load, OutOfMemoryError, malicious attack), >>>others are not affected at all. If one app needs to be upgraded or a >>>bug fix shipped, or its server restarted, again, others are not affected >>>at all. >> >> >> How do you handle the server.xml and the other configuration? Do you >> start Tomcat with an option to read a different config file, or do you >> have separate installations of Tomcat for each and every webapp? >> >> >>>Cons include inability to run these apps on the same port (this can be >>>overcome by putting a common front end, which I usually do with another >>>Tomcat running only the balancer app), and increased >>>monitoring/maintenance needed (which again can be mitigated with tools >>>like nagios). >> > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multipe Tomcat instances
If you run tomcat in a cluster where all the webapps are identical, we use the exact same (copy) of server.xml for all the tomcat instances. So when one server.xml is changed - we copy it to all of the tomcat installations. Then we rely on variable substitution in server.xml for items which might need to be specific such as ip addresses, port numbers, and worker names. We never call startup.sh directly - we have wrapper scripts which set the appropriate -D variables for us. -Tim Ryan Daly wrote: On Mon, 2004-11-29 at 14:53, Shapira, Yoav wrote: Hi, I do it this way all the time. The biggest pro is complete separation. If one app gets whacky (heavy load, OutOfMemoryError, malicious attack), others are not affected at all. If one app needs to be upgraded or a bug fix shipped, or its server restarted, again, others are not affected at all. How do you handle the server.xml and the other configuration? Do you start Tomcat with an option to read a different config file, or do you have separate installations of Tomcat for each and every webapp? Cons include inability to run these apps on the same port (this can be overcome by putting a common front end, which I usually do with another Tomcat running only the balancer app), and increased monitoring/maintenance needed (which again can be mitigated with tools like nagios). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multipe Tomcat instances
On Tue, Nov 30, 2004 at 10:39:19PM -0500, Ryan Daly wrote: : How do you handle the server.xml and the other configuration? Do you : start Tomcat with an option to read a different config file, or do you : have separate installations of Tomcat for each and every webapp? If you search the archives for CATALINA_BASE and my name, you should find a few messages in which I post an example setup based on my environment. The short version: Each Tomcat instance is a private dir with its own server.xml, (global) web.xml, webapps directory, etc. The per-instance start script sets the environment variable CATALINA_HOME to point back to the main Tomcat install (which sets the location of common/lib, server/lib, etc). -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multipe Tomcat instances
As far as Tomcat 4.x and 5.0.x, Tomcat uses %CATALINA_BASE%/conf/server.xml unless you specifically specify an alternative. Optionally, you can pass '-config fullpath' to the main method of the startup class where fullpath is the full path to your config file. For example: org.apache.catalina.startup.Bootstrap -config c:\tomcat5\conf\host1_conf.xml start Tomcat 5.5.x probably works similarly, but I haven't worked with it enough to be able to say with any authority. You can have separate tomcat installations, or just separate configs depending on what the situation calls for. >>> [EMAIL PROTECTED] 11/30/2004 9:39:19 PM >>> On Mon, 2004-11-29 at 14:53, Shapira, Yoav wrote: > Hi, > I do it this way all the time. The biggest pro is complete separation. > If one app gets whacky (heavy load, OutOfMemoryError, malicious attack), > others are not affected at all. If one app needs to be upgraded or a > bug fix shipped, or its server restarted, again, others are not affected > at all. How do you handle the server.xml and the other configuration? Do you start Tomcat with an option to read a different config file, or do you have separate installations of Tomcat for each and every webapp? > Cons include inability to run these apps on the same port (this can be > overcome by putting a common front end, which I usually do with another > Tomcat running only the balancer app), and increased > monitoring/maintenance needed (which again can be mitigated with tools > like nagios). I'm not that familiar with the balancer app. Can you explain a little or is that pretty clear somewhere in the docs? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multipe Tomcat instances
On Mon, 2004-11-29 at 14:53, Shapira, Yoav wrote: > Hi, > I do it this way all the time. The biggest pro is complete separation. > If one app gets whacky (heavy load, OutOfMemoryError, malicious attack), > others are not affected at all. If one app needs to be upgraded or a > bug fix shipped, or its server restarted, again, others are not affected > at all. How do you handle the server.xml and the other configuration? Do you start Tomcat with an option to read a different config file, or do you have separate installations of Tomcat for each and every webapp? > Cons include inability to run these apps on the same port (this can be > overcome by putting a common front end, which I usually do with another > Tomcat running only the balancer app), and increased > monitoring/maintenance needed (which again can be mitigated with tools > like nagios). I'm not that familiar with the balancer app. Can you explain a little or is that pretty clear somewhere in the docs? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multipe Tomcat instances
I would say one of the benefits is the ability to have sites using different versions of Tomcat and Java. We run two instances on our main server: one hosts our official sites, the other hosts user (student/faculty) sites. This lessens the possibility that any 'untrusted' code on our user sites can impact the availability of our official sites. Also, each instance of Tomcat can have its own security policy, and since each JVM instance is a separate OS process, each can run under an account with the minimum permissions needed by the site. When I do upgrade the JDK or Tomcat version, the user site instance tends to get it before the official site instance. If there is a problem that doesn't show up in our test environment, I'd rather take my chances having it happen to the user instance rather than the official instance. I plan to upgrade our user instance to Tomcat 5.5.4 and Java 5, but I'll wait to do our official instance until an academic break. My default web.xml is different for each instance as well: the Jasper checkInterval is more frequent for our user instance than our official instance since official developers use a development server to work out their code. In our environment, the differences between the requirements of the two hosts makes it smarter to use separate instances of Tomcat for each. >>> [EMAIL PROTECTED] 11/29/2004 1:49:35 PM >>> Does anyone have experience with setting up multiple instances of Tomcat instead of having multiple hosts being served under one instance? If anyone does, what are some pros and/or cons to doing things this way? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multipe Tomcat instances
Hi, I do it this way all the time. The biggest pro is complete separation. If one app gets whacky (heavy load, OutOfMemoryError, malicious attack), others are not affected at all. If one app needs to be upgraded or a bug fix shipped, or its server restarted, again, others are not affected at all. Cons include inability to run these apps on the same port (this can be overcome by putting a common front end, which I usually do with another Tomcat running only the balancer app), and increased monitoring/maintenance needed (which again can be mitigated with tools like nagios). Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Ryan Daly [mailto:[EMAIL PROTECTED] >Sent: Monday, November 29, 2004 2:50 PM >To: Tomcat Users List >Subject: Multipe Tomcat instances > >Does anyone have experience with setting up multiple instances of Tomcat >instead of having multiple hosts being served under one instance? > >If anyone does, what are some pros and/or cons to doing things this way? > >Thanks. > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multipe Tomcat instances
Does anyone have experience with setting up multiple instances of Tomcat instead of having multiple hosts being served under one instance? If anyone does, what are some pros and/or cons to doing things this way? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
