-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Igor,
On 5/24/16 6:52 PM, Igor Cicimov wrote: > On 24 May 2016 12:33 pm, "Christopher Schultz" > <ch...@christopherschultz.net> wrote: >> > Jakub, > > On 5/23/16 8:03 PM, Ja kub wrote: >>>> Christopher, Thx for response, pleas confirm or deny if I >>>> understand well. >>>> >>>> BIO uses thread per http connection (tcp connection). (Shame >>>> I didn't realize it!) NIO uses thread per request. > > It's more complicated than that, but very close. > >>>> With NIO thread is returned to pool as soon as request is >>>> finished (doGet ends). > > Yes. > >>>> With BIO thread is returned to pool only when tcp connection >>>> is closed !!! > > Yes, but even HTTP keepalive has a timeout, and the connection will > be dropped after that timeout, releasing the thread. > >>>> Given >>>> http://kb.mozillazine.org/Network.http.keep-alive.timeout - >>>> Amount of time in seconds to keep keep-alive connections >>>> alive. Default: 115 seconds. default tomcat keepAliveTimeout >>>> 60 s default tomcat maxThreads is 200 With 200 browsers with >>>> ajax pooling server every 50 seconds tomcat connector thread >>>> pool will be depleted and client no 201 will not be able to >>>> connect to tomcat ? > > Yes. > >> Although there is default accept queue of 100 so theoretically >> the conn 301 will be rejected. Right? Theoretically, yes. The OS has a separate accept queue, so things get a little murky when it comes to exactly which connection will be the first one rejected. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAldFr38ACgkQ9CaO5/Lv0PCehQCbBnv3VIlGsCzDvU+UTgjcc9i0 ckMAoLC9OKCMkhI7euMOdzQgZKgMAHnP =7eqe -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
