tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier ...@ice-sa.com>
Subject Re: tomcat http connector
Date Tue, 22 Nov 2011 21:26:29 GMT
Pid wrote:
> On 22/11/2011 20:08, André Warnier wrote:
>> Pid wrote:
>>> On 22/11/2011 16:21, Caldarale, Charles R wrote:
>>>>> From: Shanti Suresh [mailto:shanti@umich.edu] Subject: Re: tomcat
>>>>> http connector
>>>>> Tomcat's built-in HTTP connector can be used for production if your
>>>>> production traffic is light.  It is advisable to front-end
>>>>> Tomcat with Apache.
>>>> Sorry, that's just BS.  Back in the Tomcat 3 or 4 days, it was true
>>>> to some extent, but performance of Tomcat without httpd has been
>>>> demonstrated to be equal or better.
>>> I agree with Chuck.
>>>
>>>>> Apache's I/O is superior to Tomcat.
>>>> Another incorrect statement; with Tomcat's APR connector, the I/O is
>>>> identical - since it's all the same code.  Regardless, as Pid pointed
>>>> out, overall performance is rarely limited by the connector; the
>>>> application architecture is the critical factor.
>>> +1
>>>
>>>>> front-ending Tomcat with Apache also gives you access to the
>>>>> powerful traffic filtering, security and other modules that are
>>>>> available for Apache.
>>> Tsk, tsk.
>>>
>> -1. (to the tsk, tsk I mean).  Because that part is true.  There are a
>> whole bunch of add-on modules for Apache httpd which have no equivalent
>> (yet) in the Tomcat world.
>> (Or they are much more difficult to find).
> 
> I'm increasingly less keen on employing a jack-of-all trades approach in
> the use of HTTPD e.g. traffic filtering.  That is a network problem.
> 
> 
In the absolute, you are probably right.
But you are a Tomcat and Java specialist.

Many of the people who use Tomcat (and come to this list for help) are not Tomcat nor Java

specialists, such as sysadmins for instance.  They are asked to resolve a particular 
issue, and use the tools they know best in order to do it.
Apache httpd is more widely used and better-known to them than Tomcat, so it is their tool

of preference.
Also, in many cases, a website runs much more than Java applications and static pages.  So

they have to use another front-end anyway, and as long as it's there, they also use it 
(and its available and well-known modules) to solve issues that sometimes could also be 
handled in Tomcat, but with (to them) more difficulty.


> p
> 
> 
>>> p
>>>
>>>
>>>> And introduces configuration complexity and a greater opportunity to
>>>> create attack vectors due to seemingly innocuous configuration errors.
>>>>
>>>>  - Chuck
>>>>
>> But that's also true.
>>
>> So the real answer is, as usual, "it depends"..
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message