Rainer Jung wrote:
Jess,
I didn't really carefully think about the case of a saturated pool.
But nevertheless some hints:
1) There is always one thread waiting for the accept, which is a usual
pool thread. So an offset of one between threeads processing requests
and the pool size is normal.
Jess,
I didn't really carefully think about the case of a saturated pool. But
nevertheless some hints:
1) There is always one thread waiting for the accept, which is a usual
pool thread. So an offset of one between threeads processing requests
and the pool size is normal.
2) There is no or
H
I just redid my tests with:
BalancerMember ajp://localhost:8010 min=15 max=*50* smax=30 ttl=900
keepalive=Off timeout=900
and
and
ab -n 100 -c *50* http://jessh03l.ptcnet.ptc.com/TestApp/test.jsp?secs=3
I (after about 3 seconds) get
SEVERE: All threads (51) ar
Bill Barker wrote:
It seems that we lost building the NIO/AJP connector in Tomcat, but since i
recognize you from [EMAIL PROTECTED], you will have seen that already :). Last time
I tested, the experimental NIO/AJP connector performed better than either
the default or the APR connector on Solar
"Jess Holle" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Okay that's all starting to make some sense, but it hard to see how
> someone would come to this understanding from the documentation.
>
> I also don't see how "|connectionTimeout" will help here in that the
> documentation
Okay that's all starting to make some sense, but it hard to see how
someone would come to this understanding from the documentation.
I also don't see how "|connectionTimeout" will help here in that the
documentation says:
|
The number of milliseconds this *Connector* will wait, after
ac
"Jess Holle" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There's no intent to handle this case? Really?
>
> Tomcat should throw an "IllegalArgumentException" whenever 'acceptCount'
> is set to anything other than 0 explaining this if this is the case!
>
> If so, this is very un
There's no intent to handle this case? Really?
Tomcat should throw an "IllegalArgumentException" whenever 'acceptCount'
is set to anything other than 0 explaining this if this is the case!
If so, this is very unfortunate. We use "maxThreads" as a throttle to
limit the concurrency at this le
Yes, since you know in advance how many connections you are going to get to
the AJP connector, you can configure it so that it has enough threads to
handle all of those connections. That is why it doesn't attempt to handle
the case when the concurrency goes above maxThreads.
> -Original Me
