Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 50196 invoked from network); 12 Jan 2009 11:44:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jan 2009 11:44:40 -0000 Received: (qmail 92797 invoked by uid 500); 12 Jan 2009 11:44:35 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 92750 invoked by uid 500); 12 Jan 2009 11:44:34 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 92739 invoked by uid 99); 12 Jan 2009 11:44:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jan 2009 03:44:34 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of amirisetty.vijayaraghavan@gmail.com designates 209.85.142.185 as permitted sender) Received: from [209.85.142.185] (HELO ti-out-0910.google.com) (209.85.142.185) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jan 2009 11:44:26 +0000 Received: by ti-out-0910.google.com with SMTP id u5so8126959tia.16 for ; Mon, 12 Jan 2009 03:44:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=0fFGbfHo/Oy1qPoY0tokwscpqotRmyLE08+5XhhEwPk=; b=AxnCCdXVaue0u8WNfHN0gXxQLWnI9XD40gZQlr9e1w0On4wOdqLj+bYLkgYFcuEpZf DfUAAHiro51W8CDKEE/180nlxF0bzw8PM2XqF/f9eZ1lqtE423l9rVvQnZ0TNpYRzn4l M2jwzJPTjxt06QTMasUwdDIaY8P6PQXauWae4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dqonAXF5QwjVvObb5xx6vaaRfT9qwMLAD9N9kDR2UZsOFZvycoPa6pQf4hgD8vYmTU IzzHicJ2kY0Mkw8xd038yAhr8T1+MvgMduV07bvwgQB/du3A4Fr7LJymXMqwW7DIo2/z +RM+2lml1T/eGJsYlAEuKvjm4noIcm7YhIcBM= MIME-Version: 1.0 Received: by 10.110.53.19 with SMTP id b19mr27231247tia.53.1231760644396; Mon, 12 Jan 2009 03:44:04 -0800 (PST) Date: Mon, 12 Jan 2009 17:14:04 +0530 Message-ID: <1fdb50700901120344u6bcdd477ue0a0f08efee46381@mail.gmail.com> Subject: How does tomcat handle IOExceptions thrown by the service method From: Vijayaraghavan Amirisetty To: dev@tomcat.apache.org Content-Type: multipart/alternative; boundary=001485f02570a858140460479f51 X-Virus-Checked: Checked by ClamAV on apache.org --001485f02570a858140460479f51 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I am writing a servlet by extending the HttpServlet class. I need to over ride the doPost method to do some custom operations as required by my web application. I had a doubt regarding how Tomcat handles the IOException. Does it set the HTTP response code based upon the type of IOException that occurs while reading the request from the client ? eg, if the exception that occurs while reading the request message from the client / sending the response to the client is java.net.SocketTimeoutException, will tomcat set the status code to "408 Request Timeout", or do I have to do that explicitly ? Thanks in advance, Vijay --001485f02570a858140460479f51--