tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wade Chandler <>
Subject Re: Tomcat as a standalone webserver. Why not?
Date Thu, 01 Jun 2006 15:17:19 GMT
--- Ga�l Lams <> wrote:

> Hi,
> > I wondering if it's really so good to use Tomcat
> behind "a real" web
> > server like Apache or IIS.
> >
> > In my Tomcat 5 book there are two reasons to do it
> so:
> >
> > 1. Tomcat is not as secure as common web servers,
> especially if         you
> > want  to use CGI and SSI (I don't think I want to)
> >
> > 2. Tomcat is slow delivering static content.
> >
> > Well, as long it's just planned to use only 1
> server for my application,
> > I don't think the both points are true for me. On
> the Tomcat site
> > there's a note about performance:
> > ...
> Not an easy question, I think that the answer to
> your question is a
> mix of personal preferences and, taking into account
> your application
> specifications, whether or not you need from apache
> something that you
> can't have with Tomcat.
> I personally started with an apache/tomcat/connector
> configuration
> because the same servers were already serving
> php/mysql and cgi
> applications. We moved then all the tomcat/jsp stuff
> to its own
> servers and I decided to remove apache because:
> - it was not required anymore (reason number one)
> and for me, the
> simpler you keep things, the more robust they are.
> Also, I'm quite
> "paranoid" and for me the less stuff you installed,
> the better
> - I had some problems with the mod_jk (timeouts)
> - we are not serving static content
> Regards,
> Ga�l
As far as static content goes I don't think Apache is
really faster, it will probably use less memory, but
faster is in the details.  At least not with the more
recent Tomcat versions.  5.x.x versions that is.  I
think for anyone to say otherwise they need to have
proof readily available and it be comprehensively
comparative (or at least more than 1 configuration)
... not just some conceived notion that compiled C
code is going to run faster than Java code (look at
Transmeta processors if you need another example of a
virtual machine and speed improvements
just for an example native vs. non-native and which is
faster are all in the details as well).  The java heap
works differently from the C heap, and native
instructions at runtime are organized differently. 
Some things are faster in Java and some are faster in
C (depending on the optimizations of the java runtime
and hardware ... obviously a purely interpreted
runtime would be slower).  

Some information on the whole Java C thing:

For information about the Apache/Tomcat debate see:

I think the main point and answer comes down to Gael's
email (personal preferences and needs/which provides
you the services and configurations you need).


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message