Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 26275 invoked from network); 2 Nov 2000 23:36:11 -0000 Received: from unknown (HELO ca-ns1.eyecatching.com) (64.148.26.125) by locus.apache.org with SMTP; 2 Nov 2000 23:36:11 -0000 Received: from eyecatching.com (IDENT:gentijo@[64.148.26.114]) by ca-ns1.eyecatching.com (8.9.3/8.8.7) with ESMTP id EAA05235 for ; Thu, 2 Nov 2000 04:23:18 -0800 Sender: gentijo@ca-ns1.eyecatching.com Message-ID: <3A01F8C1.21E77332@eyecatching.com> Date: Thu, 02 Nov 2000 15:29:05 -0800 From: John Gentilin X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "tomcat-dev@jakarta.apache.org" Subject: Help, Tomcat 3.1 refusing connections Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I have developed a servlet that receives request by overiding httpServlet#service() and sends a response. The traffic back an forth is a small XML formatted block ( < 1K ). To test my servlet, I have a simple java application that formats requests and sends them to the Servlet through URL Connection. The connection is directly through Tomcat and not apache. Now if I run several iterations 20K +, I will get an occasional exception on the client side stating "Find not found" where the file specification is the URL I use to attach to my Servlet. i.e. http://localhost:8080/myServlet. I also have a custom URL mapping in my web.xml to call my servlet directly (not through invoker). There are no errors in my Tomcat log files. During the test if I run netstat -a . I see several connections in the Fin_Wait2 state. (700+ My unit test does not test for concurrency and only issues sequential requests. I have seen notes on this through Apache with a Fin_Wait2 issue with Apache Server. It states that this is just as much an operating system problem as it is the Web Server. The Web Server has a work around and I was wondering if this problem has shown up on anyone else's Tomcat Configuration and what they might of done about it. Any help would be greatly appreciated. TIA John G Configuration: Tomcat 3.1 Final Sun JDK 1.2.2 Xerces 1_2_1 Redhat 6.2 ( PII 700, 128 MB Ram)