remm 02/04/08 15:03:09
Modified: coyote/src/java/org/apache/coyote Request.java
Log:
- It seems that remoteHost and remoteAddr shouldn't be recycled after each
request, as the connection may last for more than one request/response
(and it would be the responsability of the protocol handler to set the value
whenever necessary).
Revision Changes Path
1.11 +4 -4
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Request.java
Index: Request.java
===================================================================
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Request.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- Request.java 6 Apr 2002 17:57:35 -0000 1.10
+++ Request.java 8 Apr 2002 22:03:08 -0000 1.11
@@ -463,8 +463,8 @@
queryMB.recycle();
methodMB.recycle();
protoMB.recycle();
- remoteAddrMB.recycle();
- remoteHostMB.recycle();
+ //remoteAddrMB.recycle();
+ //remoteHostMB.recycle();
// XXX Do we need such defaults ?
schemeMB.setString("http");
@@ -472,8 +472,8 @@
uriMB.setString("/");
queryMB.setString("");
protoMB.setString("HTTP/1.0");
- remoteAddrMB.setString("127.0.0.1");
- remoteHostMB.setString("localhost");
+ //remoteAddrMB.setString("127.0.0.1");
+ //remoteHostMB.setString("localhost");
instanceId.recycle();
remoteUser.recycle();
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
