On Fri, 6 Sep 2002, neal wrote: > Alright, > > So there's no taboo here that I'm not aware of. It sounds like a lot > of people do run Tomcat with Apache but not all and its simply a > matter of what fits my needs best. So, there are no silver bullet > issues (other than posibly this roon daemon thing) which suggests > running Tomcat standalone in production is foolish, right?
As I tried to suggest in an earlier reply, I don't think you can draw many definitive conclusions from polling this list on this topic. You seem to be looking for a definitive answer on this question, I'm just don't think it's so easy to come by. All you're getting are the thoughts of a handful of semi-knowledgable people. I suggest you do some more searching to see what other comments/perspectives you can find on using Tomcat standalone. For example, I went to groups.google.com and entered "tomcat standalone production" and got "about 61" matches. You can look through those and see what people say (I haven't yet). And/or you can try some other searches, there or elsewhere. And you can try it yourself for a while. Set up Tomcat standalone and see how it performs. Try to throw some twists at it functionality-wise and see how it does. Try to simulate your expected load, and see if the response/performance is acceptable. This is somewhat pioneer territory you're exploring. Regarding the running as root issue (I assume that's what you meant by "roon daemon"), that may or may not be an issue depending on your circumstances. You can either run Tomcat on port 80 as root, or run it on a non-default (for http) port, like 8080, as a safer user. There are tradeoffs either way (I'd personally shy away from running it as root -- no specific reason I can point to, just general principles -- unless you expect to have a lot of users behind proxies/firewalls who wold have trouble reaching non-default ports). > -----Original Message----- > From: Randy Secrist [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 06, 2002 2:44 PM > To: Tomcat Users List > Subject: Re: Tomcat standalone Versus Apache > > > I have heard reports, (although never seen actual numbers or data) that > suggest that if you have a lot of static pages for a large site, standalone > Tomcat decreases in performace pretty quickly. That said - Apache has also > been tested and proven with static pages, and has a great system for adding > extentions. As such, many production environments run cgi, php, and other > scripting languages for their web pages. Apache's role as a fully > serviceable http server is much more broad than the http services Tomcat > connectors provide. Tomcat connectors CAN interface with Apache to give jsp > / servlet container abilities to Apache. > > Usually, people run Apache + Tomcat so they can use multiple scripting > languages - since the entire world doesn't use java. While Tomcat does > support cgi (via servlet calls), jsp / servlet containers were not designed > with this explicitly designed as their main role - while Apache was. I have > also never heard of a servlet that imitates php...although someone who never > sleeps at night has probably implemented it. > > Randy > > ----- Original Message ----- > From: "neal" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Friday, September 06, 2002 3:24 PM > Subject: Tomcat standalone Versus Apache > > > > What do most people run for production and why? Tomcat standalone > > or Tomcat with Apache? And for that matter, isn't the http server > > for Tomcat Apache - or is it something else? > > > > John Turner mentioned the possible concern with running Tomcat as > > root. Are there any other concerns? Performance? Security? > > > > Thanks. > > Neal Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
