Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA98760 for ; Mon, 26 Jul 1999 04:42:23 -0400 (EDT) (envelope-from rachel@enlarion.demon.co.uk) Received: from enlarion.demon.co.uk ([158.152.205.157]) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 118gL0-000O56-0B for pgsql-interfaces@postgresql.org; Mon, 26 Jul 1999 08:42:22 +0000 Sender: rachel Message-ID: <379C1DE6.7FAE7173@enlarion.demon.co.uk> Date: Mon, 26 Jul 1999 09:35:50 +0100 From: Rachel Greenham Organization: Tris Global Communications ltd X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.10 i586) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: JDBC problem - again Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter, did you ever get around to ensuring a closed connection when a Connection object is finalised? I've just hit the problem again, with Postgres dying of too many open connections. I thought I'd fixed it on my client code by always closing the Connections before they go out of scope, but evidently not, one is hiding somewhere taking about a fortnight to happen enough to kill Postgres, and it's going to be a bitch to track down - and I really can't see the harm in the connection being closed on finalise. -- Rachel