tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/server
Date Sun, 17 Apr 2005 20:46:54 GMT

----- Original Message ----- 
From: "Remy Maucherat" <>
To: "Tomcat Developers List" <>
Sent: Sunday, April 17, 2005 12:22 PM
Subject: Re: cvs commit: 
jakarta-tomcat-connectors/jk/java/org/apache/jk/server wrote:
>> Give Remy something meaningful to benchmark against ;-).
>Mladen did all the preliminary tests using the HTTP example server that is 
>in the mustang sources, which is a similar comparison.
>> It also has extra GC vs Remy's ChannelAprSocket.
>... which will never exist ;)
>I don't think the way AJP connections are currently processed makes this 
>suitable for this kind of usage, as the GC would likely be too high. Did 
>you test it ?

On Solaris, threads are really cheap, so ChannelSocket would alway win 
anyway (just on the context-switching alone :).  And, yes, the GC is too 

The only use-case for ChannelNioSocket would be a system where you are 
forced to set a connectionTimeout for ChannelSocket to keep Tomcat happy, 
and what that is telling you is that you really need a better OS.

I admit that it was somewhat of a vanity project (like a lot of stuff in Jk 
:), but since almost nobody knows Jk-Coyote well enough to enable it, it 
seemed harmless. I also have no problem yanking it if all it's going to do 
is to create tomcat-user questions.

>I'll implement the APRized AJP using the same infrastructure (AprEndpoint) 
>and architecture as the HTTP connector, which means socket only.
>Right now, I'm having more fun trying to add sendfile support (with ranges 
>support). I'll have to make small changes in DefaultServlet to enable it, 
>but nothing that would imapct the default behavior, of course.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message