Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 79202 invoked from network); 22 Dec 2010 16:44:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Dec 2010 16:44:45 -0000 Received: (qmail 44627 invoked by uid 500); 22 Dec 2010 16:44:42 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 44308 invoked by uid 500); 22 Dec 2010 16:44:39 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 44299 invoked by uid 99); 22 Dec 2010 16:44:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Dec 2010 16:44:38 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 22 Dec 2010 16:44:36 +0000 Received: (qmail 79118 invoked by uid 99); 22 Dec 2010 16:44:14 -0000 Received: from localhost.apache.org (HELO [192.168.23.9]) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Dec 2010 16:44:14 +0000 Message-ID: <4D122AD4.5020000@apache.org> Date: Wed, 22 Dec 2010 16:44:04 +0000 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat 6.0.18 related NIO questions. References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 22/12/2010 16:31, shrikant patel wrote: > We are using tomcat connector as follows --> > > Based on the documentation we are using the blocking call, right? It depends. Probably the BIO connector but it could also bee the APR connector. The logs will tell you which. > I have basic understanding of NIO. My understanding is that tomcat > internally use Java NIO to read the request into buffer. When complete > request is read then dispatch it to servlet for processing. That way each > servlet thread is not blocked on IO. Similarly in case of response, it get > response from servlet, keep buffering it and send it to client. This way > servlet is not completely blocked for entire duration of the response being > send to client. > Please let me know if this is correct. No. That is wrong. There is more (simulated) blocking I/O happening than you think. > Is there document in this regards you can point to get better understanding? Bottom of this page. http://tomcat.apache.org/tomcat-6.0-doc/config/http.html Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org