Bug 362 - When a connectino is reset, tomcat should retry sending the response object instead of re-executing the entire jsp. BugRat Report#648
Summary: When a connectino is reset, tomcat should retry sending the response object i...
Status: CLOSED LATER
Alias: None
Product: Tomcat 3
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 3.2.1 Final
Hardware: All All
: P1 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-21 15:25 UTC by Christian Mattix
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomcat Developers Mailing List 2000-12-21 15:25:36 UTC 
When a when a jsp response is asked to be resent because of a "connection reset by peer" only the response object should be resent again. Currently the JSP is re-executed, which can lead to unpredictable results if the jsp is requesting or changing data on a 3rd process. Consider:

jsp code:
--------
<snip>
  someServer = (ServerInterface)Naming.lookup(serverURL);
  someServer.incrementConnections();
<snip>

If the jsp is executed again because of a connection reset, then incrementConnecions() will be executed again. This is not desired behavior.
Comment 1 Marc Saegesser 2001-03-21 12:08:50 UTC 
This won't be addressed for 3.2.2 but will be considered for a later release.
Comment 2 Costin Manolache 2001-04-22 10:39:54 UTC 
I think the current behavior is correct - HTTP is stateless, shouldn't care
if a previous request failed because of connection reset. The user code should
handle this - for example by using transactions or checking. In general, this 
is a known ( and intended ) behavior of HTTP.
I'm closing this as invalid
Comment 3 Ignacio J. Ortega 2001-11-06 07:58:25 UTC 
*** Bug 4676 has been marked as a duplicate of this bug. ***