It occurred to me to put Tomcat in front of Apache. Why? Because I'm on Windows 2000.
And, Apache 1.x with mod_perl is a single-threaded dog that even ASF does not
recommend using for production. Apache 2 and mod_perl beta is out but nonone can tell
me if it is ready for prime time on Windows (or when it will be). So I'm rolling the
dice whichever way I go. We have been on Apache 1.x with mod_perl for several years
and it is reliable, but not multi-user friendly. Our load is very low but the current
solution will not scale. I have 3 static pages and the whole rest of the system
(almost) is written in perl to run under mod_perl. I inquired about the possibility
of doing a mod_perl for Tomcat and I got poopooed. On unix they have none of the
problems I have, so they can stay on Apache 1 and play around with Apache 2 for the
next decade.
The way I see it, the Apache/mod_perl/perl camp wrote all their stuff in C language
for performance - which is fine. Its fine until your stuck in "betaland" for 4 years
because Windows is hind tit in Apacheland, and few windows programmers can help with
C. Java may be a bit slower, but the clustering and load balancing might be better
with just Tomcat. The connector between Apache and Tomcat will work for me, but it
doesn't solve my single-thread issue if I have to stay on Apache1.x. Also, I need to
run ssl all the time because of the customer's requirement. Windows is hind tit in
mod_ssl land also. The mod_ssl list often responds with a lecture on how stupid you
are for using Windows instead of offering any useful help. So, support is a supreme
factor in the decision on architectures. If you can't fix it yourself, you are not
necessarily any better off than if you use a closed source product.
So, I'm thinking it may be better to put Apache in the back, so it can be phased out.
That's my 2 cents.
Chuck
-----Original Message-----
From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 4:26 PM
To: Tomcat Users List
Subject: RE: Tomcat and IIS
This issue of Tomcat and Apache comes up over and over and over again on
the list here because everyone tells everyone else that they should run
Apache in front of Tomcat without understanding what the person is
doing. There are definitely reasons for this (which have been discussed
more than many times), but I have *never* seen anyone give _conclusive_
*performance-centric* proof for this.
I agree -- conceptually it gives you performance boost after some activity
threshold, but I surmise that the *large majority* of people out there
aren't even close to this threshold. It seems to me that it's more of a
"common knowledge" thing than anything. The more often something is
repeated, the more likely it will become defacto truth.
In fact, our app supports connections both through a proxy (IIS or Apache)
*and* directly to Tomcat because response times are very important to us
and the turnaround going through Apache is ~100ms while the turnaround
directly to Tomcat is ~20ms. Tomcat is an excellent HTTP server. It
easily supports the requirements of most projects out there. IMHO, using
Tomcat as Http server should be the default and Apache should only be used
if you have a specific reason to use it (of which there are many very real,
very valid ones, some of which Jeffrey Peloquin, amongst others, have
mentioned in this thread).
My point in writing this is that we should all be careful what we suggest
before understanding what exactly the person needs. And, quite frankly,
those asking should find these threads *easily* with a little effort. ;)
justin
At 03:26 PM 3/27/2003, you wrote:
>What if the majority of your pages are either servlets or JSP. I have only a
>couple pages that are not dynamically created, so Apache will only handle
>those, right? I'm running in a pure Tomcat environment because of this...
>and the fact I don't know how to set up apache with tomcat :-)
>
>-Brian
>
>-----Original Message-----
>From: Jeremy Whitlock [mailto:[EMAIL PROTECTED]
>Sent: Thursday, March 27, 2003 3:23 PM
>To: 'Tomcat Users List'
>Subject: RE: Tomcat and IIS
>
>
>That's possible BUT performance will suffer. Tomcat isn't as powerful
>as Apache. If you are running a small website, intranet and such,
>Tomcat would probably work fine but it's not Commercially fit as a Web
>Server. Apache on the other hand is. Later, J
____________________________________
Justin Ruthenbeck
Software Engineer, NextEngine Inc.
justinr - AT - nextengine DOT com
Confidential
See http://www.nextengine.com/confidentiality.php
____________________________________
---------------------------------------------------------------------
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]
