Bug report #648 has just been filed. You can view the report at the following URL: <http://znutar.cortexity.com/BugRatViewer/ShowReport/648> REPORT #648 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: critical Confidence: public Environment: Release: Tomcat 3.2 JVM Release: JDK 1.3 Operating System: Windows NT4.0 OS Release: NT4 service Pack 6 Platform: Windows Synopsis: When a connectino is reset, tomcat should retry sending the response object instead of re-executing the entire jsp. Description: 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.Title: BugRat Report # 648
BugRat Report # 648
| Project: Tomcat | Release: Tomcat 3.2 |
| Category: Bug Report | SubCategory: New Bug Report |
| Class: swbug | State: received |
| Priority: medium | Severity: critical |
|
Confidence:
public
|
Submitter:
Christian Mattix ( [EMAIL PROTECTED] )
Date Submitted:
Dec 21 2000, 03:25:36 CST
Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )
- Synopsis:
- When a connectino is reset, tomcat should retry sending the response object instead of re-executing the entire jsp.
- Environment: (jvm, os, osrel, platform)
- JDK 1.3, Windows NT4.0, NT4 service Pack 6, Windows
- Additional Environment Description:
- Report Description:
-
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:
--------
someServer = (ServerInterface)Naming.lookup(serverURL); someServer.incrementConnections(); If the jsp is executed again because of a connection reset, then incrementConnecions() will be executed again. This is not desired behavior.
