yes, I've ran 20 instances of ab (each with 50 connections) at the same
time on my windows box, so 1000 concurrent connections. (with tomcat's
default maxThread setting, which I think was 200)
The NIO connector handles this fine, my box is of course 100% cpu between
windows,tomcat and all the ab pr
I'm not seeing the windows problems, I used to have many problems on
windows using jdk1.4, but since 1.5 I have no problems at all. I do have a
brand new machine, so maybe there is some windows patch on it that I
didn't have before, other than that I can't think of anything.
I'm showing almost ide
man that sucks,
I can run the same tests, even hundred thousand iterations, I get a little
worse performance than the blocking connector and a little better than the
APR connector, and it never crashes for me.
I'm in dublin at apachecon this week, but will continue as soon I get back,
have a good
let me fill in the other blanks,
the connector will be modified so that it knows when it has enough data to
proceed, ala, chunked encoding etc.
that is still work to be done.
but I wanted let you know how it conceptually could look similar to the
APR connector, and how much of the code could be sh
So it uses NIO to increase concurrency, ie, have more connections open
than threads, same way as APR, but writing to the stream is not done non
blocking, it still follows the request/response/1-thread model
still lot of work to do
Filip
>>
>>
>>> -Original Message-
>>> From: Filip Hanik
>
>
>> -Original Message-
>> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
>> Sent: Monday, June 19, 2006 6:31 AM
>> To: Tomcat Developers List
>> Subject: NIO Connector, please review
>>
>> gents,
>> I've worked on an NIO connector, since the NIO and APR model
>> can be/are
>> ve
I would love to backport it to Tc5.5 and that way also have Comet support
in tc5.5.x
Filip
> +1 - I'm also working on a nio connector ( it is in sandbox ), but the
> goals
> are quite different,
> I want to have it simpler and smaller than the apr model. I think
> old-style
> connector
> should
> It implements aTCP/IP Socket receiver without NIO. This classes very
> useful for async mode at some linux platforms. Please, don't remove
> them, they are very important for some user.
ok, no problem. I will leave them in.
>
> I think also we must discuss the next steps to change the cluster c
I've been getting a good amount of emails regarding the clustering system
being broken in Tomcat 5.5, so I thought I make the announcement here so
that we can clear the air once and for all.
In tomcat 5.5.10 the underlying communication protocol for the clustering
system changed, and not only made
