tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry Isaacs" <Larry.Isa...@sas.com>
Subject RE: tomcat 3.3.1 ThreadPool Bug?
Date Wed, 23 Oct 2002 02:59:53 GMT
The property name is case sensitive.  Thus,

	maxThreads="256"

will work, but

	maxthreads="256"

won't.

Cheers,
Larry

> -----Original Message-----
> From: Nagesh Nayudu [mailto:nagesh@supportsoft.com] 
> Sent: Tuesday, October 22, 2002 9:52 PM
> To: 'Tomcat Users List'
> Subject: tomcat 3.3.1 ThreadPool Bug?
> 
> 
> Hi,
> I am running Tomcat3.3.1 on Solaris. I specified the 
> maxthreads for the
> AJP13 connector as 256. But, when I load test the web.app., I 
> get a log
> message in stdout:
> ThreadPool: All threads are busy, waiting. Please increase 
> maxThreads or
> check the servlet status200 200
> 
> Looks like the max threads specified in server.xml is 
> ignored, and tomcat
> uses the default value of 200. I searched the bug database 
> but, did not find
> this bug reported. Has this bug been fixed in later releases 
> of 3.3.1? I can
> not start using 4.x version even if this has been fixed in it. Thanks.
> 
> -Nagesh.
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-user-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:tomcat-user-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message