Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 82700 invoked from network); 23 Apr 2002 19:59:37 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Apr 2002 19:59:37 -0000 Received: (qmail 27661 invoked by uid 97); 23 Apr 2002 19:59:35 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 27619 invoked by uid 97); 23 Apr 2002 19:59:35 -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 27606 invoked by uid 50); 23 Apr 2002 19:59:34 -0000 Date: 23 Apr 2002 19:59:34 -0000 Message-ID: <20020423195934.27605.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 8433] New: - mod_webapp choking on concurrent requests X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8433 mod_webapp choking on concurrent requests Summary: mod_webapp choking on concurrent requests Product: Tomcat 4 Version: 4.0.2 Final Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Connector:Webapp AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: cavan.morris@worldnet.att.net I'm running tomcat 4.0.2 under apache 2.0.32 with webapp-module-1.0.2-tc402 on redhat 7.2 and jdk 1.4 I'm using the apache "ab" program for perfomance testing and have noticed that the sockets between apache and tomcat seem to die when I use concurrent requests. Somtimes I have to restart the servers in order to get a response from them again. Here's the ab command that will cause the problem: ./ab -v 2 -n 20 -c 2 MY_HOST/index.jsp Here are the exceptions from the tomcat logs: 2002-04-23 11:38:02 WarpHost[MY_HOST]: Mapping request for Host 2002-04-23 11:38:02 WarpEngine[Apache]: Mapping request 2002-04-23 11:38:02 WarpHost[MY_HOST]: Mapping request for Host 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConnector] Connection from /127.0.0.1:33290 to /127.0.0.1:8008 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConnector] Connection from /127.0.0.1:33292 to /127.0.0.1:8008 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConfigurationHandler] Invalid packet with type 16 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConnection] Exception on socket java.io.IOException: Premature packet header end at org.apache.catalina.connector.warp.WarpConnection.recv (WarpConnection.java:237) at org.apache.catalina.connector.warp.WarpRequestHandler.handle (WarpRequestHandler.java:113) at org.apache.catalina.connector.warp.WarpConnection.run (WarpConnection.java:194) at java.lang.Thread.run(Thread.java:536) 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConnection] Exception on socket java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:105) at org.apache.catalina.connector.warp.WarpConnection.send (WarpConnection.java:220) at org.apache.catalina.connector.warp.WarpConfigurationHandler.handle (WarpConfigurationHandler.java:246) at org.apache.catalina.connector.warp.WarpConnection.run (WarpConnection.java:189) at java.lang.Thread.run(Thread.java:536) 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConfigurationHandler] Filter mappings (0) 2002-04-23 11:38:02 [org.apache.catalina.connector.warp.WarpConfigurationHandler] Filter mappings (0) 2002-04-23 11:38:02 WarpEngine[Apache]: Mapping request Changing the number of requests to perform from 20 to 100 will make it so that I have to restart apache to get a response from the host. -- To unsubscribe, e-mail: For additional commands, e-mail: