tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Doe" <>
Subject Re: Tomcat as standalone
Date Mon, 13 Dec 2004 13:38:50 GMT
Putting Apache on an Internet-visible network, and having this route its 
traffic to Tomcat on a local network on your website (eg a 10, 172 or 
192.168 address) can improve your security no end. There is no direct way to 
your Tomcat server. As long as you have tightend your code for SQL and HTML 
scams, you will have a very safe environment. Of course this means a second 
server and so more cost, but if you want a Rolls-Royce solution...



>From: Ben Souther <>
>To: Tomcat Users List <>
>Subject: Re: Tomcat as standalone
>Date: Mon, 13 Dec 2004 00:54:52 -0500
>Since 90% of your app is dynamic, there is a good chance that
>Tomcat as a standalone may actually be more efficient. The work
>the webserver and connector has to do to pass the requests/responses
>back and forth to tomcat is all in addition to what Tomcat would have to
>do anyway.
>I would recommend giving Tomcat as a standalone a shot.
>If you feel you need more performance, look into your options.
>Putting a webserver in front of Tomcat is one of them.  Load balancing,
>heavier hardware, clustering, are some others.
>Remember, Tomcat, The Apache Web Server, and the connectors needed to
>join the two don't have the same release cycles.  Besides performance,
>you also want to consider maintenance and upkeep costs.
>If you want to be real thorough, set up both scenarios and compare them
>under load. Set up SSL under both scenerios. Also compare the effort to
>get them up and running.  Then also take a look at the open bug list for
>Tomcat to see how many issues are related to connectors.  Look at the
>release cycles for tomcat, apache, and the connectors. Then look at how
>much time you have budgeted for maintaining each setup.
>Without looking at your app, hardware and business plan, nobody can tell
>you for certain which way to go.
>One thing to be aware of. There is a lot of outdated information on the
>web claiming that Tomcat as a standalone is not ready for production.
>If you come across one of these sites, make sure you know either when it
>was written or what version of Tomcat they're talking about. Both Tomcat
>and the JVMs needed to run it have made great strides in recent years.
>What was accurate at the time it was written may be very inaccurate now.
>On Sun, 2004-12-12 at 23:33, Dola Woolfe wrote:
> > It 90% of my website is dynamic, is it a good idea to
> > skip the apache server altogether and just run Tomcat
> > alone on port 80?
> >   Seems like a good idea: one few application to worry
> > about, no headache with connecting apache and tomcat
> > (which I still haven't figured out how to do with 5.x)
> > and so forth.
> >
> > Please, any opinions.
> >
> > Also is 5.5 ready for prime-time?
> >
> > Thank you very much in advance.
> >
> > Dola
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Take Yahoo! Mail with you! Get it on your mobile phone.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> >
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Express yourself instantly with MSN Messenger! Download today it's FREE!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message