tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hermes Flying <flyingher...@yahoo.com>
Subject Re: Fw: Can not understand how maxThreads of Connectors works
Date Fri, 25 Jan 2013 19:58:10 GMT
Hi,
I actually deploy in 2 servers one in 6 and one in 5. I noticed the same behavior described
(that was not believed).
I did not aim in taking anyone's time.
All I wanted to do is verify the functionality using really small values.
In a previous mail it was written by someone that he tested this in 6 and he said the browser
stuck.
I did not notice that.




________________________________
 From: Christopher Schultz <chris@christopherschultz.net>
To: Tomcat Users List <users@tomcat.apache.org> 
Sent: Friday, January 25, 2013 9:34 PM
Subject: Re: Fw: Can not understand how maxThreads of Connectors works
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hermes,

On 1/25/13 4:16 AM, Hermes Flying wrote:
> I am using the correct server.xml. In the version 5.5.36 the 
> maxThreads of 0 has no effect due to this code in 
> org.apache.tomcat.util.net.PoolTcpEndpoint

You said you were using Tomcat 6. Now you say you are using Tomcat
5.5.36. This is why I asked (long ago) to give us exact versions.

> So what I observe is correct. I.e. with 0 there is no error and
> also my web application works fine since it defaults to 200
> threads. Will check this out in Tomcat 6

Maybe then we'll finally be on the same page.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEAREIAAYFAlEC3kIACgkQ9CaO5/Lv0PBZUQCfWTYi3fmEi45N+wWGCVqz+yGf
4ZUAn1CdzM0CexovENDj3YJBhYCa1JIG
=Gc1n
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message