Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 91387 invoked from network); 20 Jun 2003 03:13:28 -0000 Received: from wrath.forked.net (216.65.131.190) by daedalus.apache.org with SMTP; 20 Jun 2003 03:13:28 -0000 Received: from wrath.forked.net (IDENT:fredgers@localhost [127.0.0.1]) by wrath.forked.net (8.12.6/8.12.6) with ESMTP id h5K3DXuM032496 for ; Thu, 19 Jun 2003 20:13:33 -0700 Received: from localhost (fredgers@localhost) by wrath.forked.net (8.12.6/8.12.6/Submit) with ESMTP id h5K3DXm0032493 for ; Thu, 19 Jun 2003 20:13:33 -0700 Date: Thu, 19 Jun 2003 20:13:33 -0700 (PDT) From: Fred Gerson To: torque-user@db.apache.org Subject: large number of CLOSE_WAIT connections Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hey all, I noticed a very large number (about 100) of CLOSE_WAIT status tcp connections to my mysql server, something that was obviously eating up system resources on my box. This came from leaving the Turbine2.2/Torque app unmonitored for a while. I have since restarted the application and the CLOSE_WAITs have closed, but I'd like to find a more permanent solution to the problem. Did I configure something incorrectly? I have defaultMaxConnections=10 maxExpiryTime=3600 connectionWaitTimeout=10 in Torque.Properties Could I maybe have written bad application logic in my Turbine app that may be causing this? I'm on a RH7.3 box, with MySQL 3.23.55 and the org.gjt.mm.mysql.Driver driver. Thanks, Fred