Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 84438 invoked from network); 2 Nov 2001 00:04:11 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 2 Nov 2001 00:04:11 -0000 Received: (qmail 21070 invoked from network); 2 Nov 2001 00:06:31 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 2 Nov 2001 00:06:31 -0000 Received: (qmail 10032 invoked by uid 97); 2 Nov 2001 00:04:02 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 9998 invoked by uid 97); 2 Nov 2001 00:04:01 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 9987 invoked from network); 2 Nov 2001 00:04:01 -0000 Message-ID: <01af01c1632c$f7f453e0$5a66a8c0@wilshire.com> Reply-To: "Bill Barker" From: "Bill Barker" To: "Tomcat Developers List" References: Subject: Re: How does Tomcat handle discarded-request Date: Thu, 1 Nov 2001 15:28:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 X-Archived: msg.XXtCnWMa@sneezy X-Filter-Version: 1.4.5 (sneezy) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Generally with 3.2.x it will throw there, but it may throw later due to buffering. And since the browser has closed the connection, no you can't send/receive anything further. Of course, there is nothing to prevent you inclosing your code in a try {} finally {} block if workBean needs to do cleanup. ----- Original Message ----- From: "Hu, Xuebing" To: "Tomcat Developers List" Sent: Thursday, November 01, 2001 2:39 PM Subject: RE: How does Tomcat handle discarded-request > Hi, Craig, > > Here is my skeleton jsp, > > > > > <% > Object param1=getParameter("Param1") ; > ... > Object paramn = getParameter("Paramn") ; > > // let us say that doWork takes a few minutes to finish > // and I just can not wait at the browser side and I issues another request to TOMCAT > Object result = workBean.doWork(param1, ..., paramn) ; > > // Is IOException thrown out here? > out.println(result) ; > %> > > As per your explaination, is IOException thrown out on out.println()???, since it is JSP, so my workBean has no way to talk to something at the browser side to get data. > > thanks, > David > > > ---------- > > From: Craig R. McClanahan[SMTP:craigmcc@apache.org] > > Reply To: Tomcat Developers List > > Sent: Thursday, November 01, 2001 5:08 PM > > To: Tomcat Developers List > > Cc: Hu, Xuebing > > Subject: RE: How does Tomcat handle discarded-request > > > > > > > > On Thu, 1 Nov 2001, Hu, Xuebing wrote: > > > > > Date: Thu, 1 Nov 2001 17:03:29 -0500 > > > From: "Hu, Xuebing" > > > Reply-To: Tomcat Developers List > > > To: Tomcat Developers List > > > Subject: RE: How does Tomcat handle discarded-request > > > > > > Thanks, Bill for the response. Any detail? I am currently using TOMCAT 3.2.3. > > > > > > > In general, you cannot count on the server even knowing that the request > > was cancelled. The following scenarios are all possible: > > > > * The entire request was read before the cancel happened, so no > > notification is possible until the response is written back out > > and receives an IOException. (This is by far the most common case.) > > > > * Tomcat was able to read the headers, but does not need to read > > the data. In this case, it is the application (not Tomcat) that > > would receive an IOException when trying to process the input > > stream. Therefore, it is up to your application to respond > > appropriately. > > > > * Tomcat was unable to read the headers (because the cancel happened > > very quickly). It will typically log an exception and throw the > > request away. > > > > > David > > > > > > > Craig > > > > > > -- > > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > *----* This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. -- To unsubscribe, e-mail: For additional commands, e-mail: