Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 1143 invoked from network); 12 Dec 2001 19:58:08 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Dec 2001 19:58:08 -0000 Received: (qmail 6037 invoked by uid 97); 12 Dec 2001 19:58:04 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 6021 invoked by uid 97); 12 Dec 2001 19:58:03 -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 6009 invoked from network); 12 Dec 2001 19:58:03 -0000 From: "Keith Wannamaker" To: Subject: ajpv12 socket closure Date: Wed, 12 Dec 2001 14:59:16 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've been debugging a socket problem in ajpv12 (NT) where bits are being written by Tomcat to the socket (back to mod_jk), but jk's read fails with a SHUTDOWN. It's as if the bits don't quite make it onto the wire, and the socket closure is a hard close. I thought the point of so_linger was to specify the amount of time to try to send the queue bits onto the wire prior to closing the socket. Wouldn't this indicate that the present value (100) is too small? The relevant t-d thread is http://w6.metronet.com/~wjm/tomcat/2000/Sep/msg00151.html Thanks for any info, Keith -- To unsubscribe, e-mail: For additional commands, e-mail: