> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: RE: Solaris 10 Tomcat performance maxes out at 2 threads
>
> As it turns out the default behavior of a .Net application is to set a
> default connection limit of 2?!?!?
This is the limit recommended (not required)
Hi John,
[EMAIL PROTECTED] wrote:
As it turns out the default behavior of a .Net application is to set a
default connection limit of 2?!?!? (I guess this explains why IE and
Firefox default to 2 connections). Not being a .Net expert I didn't realize
this - but when we did a netstat on the server
> From: Caldarale, Charles R <[EMAIL PROTECTED]>
>> From: Caldarale, Charles R <[EMAIL PROTECTED]>
>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>> Subject: Solaris 10 Tomcat performance maxes out at 2 threads
>>>
>>> We see thr
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: RE: Solaris 10 Tomcat performance maxes out at 2 threads
>
> I have a poor understanding of how Tomcat spawns/manages
> threads.
It's pretty simple, all under control of the attributes on the
elements
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Subject: Solaris 10 Tomcat performance maxes out at 2 threads
>>
>> We see throughput increase when we go from 1 client thread to
>> 2 client threads, but when we run more than 2 th
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: Solaris 10 Tomcat performance maxes out at 2 threads
>
> We see throughput increase when we go from 1 client thread to
> 2 client threads, but when we run more than 2 threads we see
> no additional throughput.
Fi
I am running Tomcat 5.5 on a 4 CPU Sun Fire v440 system running Solaris 10.
My client is a Windows application that is issuing web service requests via
keep alive connections.
We see throughput increase when we go from 1 client thread to 2 client
threads, but when we run more than 2 threads we s
