Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 22286 invoked by uid 500); 27 Apr 2001 07:51:51 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 22244 invoked from network); 27 Apr 2001 07:51:49 -0000 From: "Aleksey Studnev" To: Subject: [BUG Report Tomcat 3.2] Reset connection with client Date: Fri, 27 Apr 2001 11:51:38 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N os : windows NT servlet container : tomcat 3.2 release Client wants to re-use socket connection for multiple requests from server - it is actually a feature of HTTP 1.1. This saves time on creating socket object, making TCP connection. What Tomcat is doing unlike other web servers we have ( Apache, Weblogic) is resetting connection after every request. The sequence which is seen in the network is the following: Client -> Connect Client -> GET(socket NNN) Tomcat -> Response Client -> GET(socket NNN) Tomcat -> Reset connection <- BUG is HERE! Client -> Connect Tomcat -> Bind Client -> GET(socket MMM) Tomcat -> Response You probably do not notice this bug with IE or Netscape because they make a new connection on every page reload. Aleksey