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
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 a
o:[EMAIL PROTECTED]
Sent: Thursday, June 14, 2007 2:58 PM
To: Tomcat Developers List
Cc: Dobson, Simon; Wang, Andy; Fenlason, Josh
Subject: Serious non-native AJP connector issue
We're facing a /serious /issue with the non-native AJP connector.
To put it most simply, some requests seem to "ge
Original Message-
> From: Jess Holle [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 14, 2007 2:58 PM
> To: Tomcat Developers List
> Cc: Dobson, Simon; Wang, Andy; Fenlason, Josh
> Subject: Serious non-native AJP connector issue
>
> We're facing a /serious /issue
We're facing a /serious /issue with the non-native AJP connector.
To put it most simply, some requests seem to "get lost" in Tomcat in
various cases involving concurrent requests -- and not egregious numbers
of concurrent requests, either.
For instance,
1. Use a Tomcat 5.5.23 with a config
10 matches
Mail list logo
