From owner-freebsd-ports Thu Apr 19 1:47:53 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mailin10.bigpond.com (juicer35.bigpond.com [139.134.6.87]) by hub.freebsd.org (Postfix) with ESMTP id E2FBD37B422 for ; Thu, 19 Apr 2001 01:47:49 -0700 (PDT) (envelope-from deece@newmillennium.net.au) Received: from picard.dyn.newmillennium.net.au ([139.134.4.58]) by mailin10.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GC17C900.EJ0 for ; Thu, 19 Apr 2001 18:52:57 +1000 Received: from CPE-61-9-175-14.vic.bigpond.net.au ([61.9.175.14]) by mail1.bigpond.com (Claudes-Little-MailRouter V2.9c 1/4334374); 19 Apr 2001 18:46:59 Received: from localhost (deece@localhost) by picard.dyn.newmillennium.net.au (8.11.3/8.11.3) with ESMTP id f3J8ffE76892 for ; Thu, 19 Apr 2001 16:41:42 +0800 (WST) (envelope-from deece@newmillennium.net.au) Date: Thu, 19 Apr 2001 16:41:41 +0800 From: "Alastair D'Silva" X-X-Sender: To: Subject: Apache13-modssl & mod_php4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have recently upgraded Apache/modssl via the ports collection to 1.3.19-2.8.2. This seems to have broken persistent connections to my PostgreSQL database. It seems that while persistent connections open fine, they are not being returned to the pool for reuse, the end result being that PostgreSQL eventually starts refusing connections. I have reproduced this behavior on 3 machines, all running different versions of 4.2-STABLE. I have temporarily changed my code to not use persistent connections, but I don't consider this to be a proper fix. Can anyone suggest a better solution? Cheers, -- Alastair D'Silva Networking Consultant New Millennium Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message