Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 98011 invoked from network); 6 Jul 2000 17:20:17 -0000 Received: from unknown (HELO orange.agentscape.de) (@62.96.193.18) by locus.apache.org with SMTP; 6 Jul 2000 17:20:17 -0000 Received: from agentscape.de (cherry.agentscape.de [192.168.101.25]) by orange.agentscape.de (8.9.3/8.8.7) with ESMTP id TAA08813 for ; Thu, 6 Jul 2000 19:28:23 +0200 Message-ID: <3964BF8F.9C24C461@agentscape.de> Date: Thu, 06 Jul 2000 19:19:11 +0200 From: Markus Nietfeld Organization: PopNet Agentscape AG X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-user@jakarta.apache.org Subject: Tomcat 3.1 shutting down connection? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi folks, we are evaluating Tomcat 3.1 for a customer project, where we use open HTTP connections as push channel to the client browser. Thus, Tomcat is listening at port 8080 as standalone HTTP server. It seems to be pretty stable, but from time to time we get the following exception: java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:423) at java.net.ServerSocket.implAccept(ServerSocket.java:191) at java.net.ServerSocket.accept(ServerSocket.java:174) at org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(SimpleTcpEndpoint.java:267) at org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(SimpleTcpEndpoint.java:248) at org.apache.tomcat.service.TcpListenerThread.run(SimpleTcpEndpoint.java:319) at java.lang.Thread.run(Thread.java) Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] shutdown due to exception: java.net.SocketException: Connection reset by peer After that, Tomcat is not reachable anymore, although the servlets inside still seem to be alive (pingable via RMI). We have installed Tomcat 3.1 Final on a Linux Kernel 2.2.14, using IBM's JDK 1.1.8. We are using Tomcat's SimpleTcpConnector. I did not play yet with the PoolConnector and the JVM optimizations mentioned in the User's Guide, but I can hardly imagine that this problem is connected to not using a threadpool (as we are only three people testing simultaneously ;) Does anyone have similar experiences? Thanks for any help, Markus. -- Dipl.-Inform. Markus Nietfeld Software Development PopNet Agentscape AG (http://www.popnet-agentscape.de) Kaiserin-Augusta-Allee 10-11, D-10553 Berlin fon: ++49-30-5900478-27, fax: ++49-30-5900478-99