Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of Raja.Kulasekaran@netapp.com
 designates 216.240.18.37 as permitted sender)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: DBI Connectons accumulate under Mod_perl
Date: Wed, 11 Nov 2009 11:04:55 +0530
Message-ID: 
 <CF4B8324B5D2934C9377BD36E370526B0A3ED18E@BTCMVEXC1-PRD.hq.netapp.com>
In-Reply-To: <2E99EB9D-8E5C-4255-B72D-958C3E66C4D5@kineticode.com>
Thread-Topic: DBI Connectons accumulate under Mod_perl
Thread-Index: AcpiLAEq/IBxp8NOSMWaTGsO4gM96QAZG9+g
References: <4ADDEC61.2080300@itlegion.ru>
 <CF4B8324B5D2934C9377BD36E370526B0A2C7645@BTCMVEXC1-PRD.hq.netapp.com>
 <4AF9810E.9050001@itlegion.ru>
 <1440789C-0B10-44FC-A6CE-6256FA08EE85@kineticode.com>
 <CF4B8324B5D2934C9377BD36E370526B0A2C7D04@BTCMVEXC1-PRD.hq.netapp.com>
 <2E99EB9D-8E5C-4255-B72D-958C3E66C4D5@kineticode.com>
From: "Kulasekaran, Raja" <Raja.Kulasekaran@netapp.com>
To: "David E. Wheeler" <david@kineticode.com>
Cc: "Artem Kuchin" <matrix@itlegion.ru>, <modperl@perl.apache.org>

I'm connecting against oracle. So for every request it establish the
connection and it remains stable even though the request=20
has been completed successfully .=20

-Raja=20

-----Original Message-----
From: David E. Wheeler [mailto:david@kineticode.com]=20
Sent: Tuesday, November 10, 2009 11:03 PM
To: Kulasekaran, Raja
Cc: Artem Kuchin; modperl@perl.apache.org
Subject: Re: DBI Connectons accumulate under Mod_perl

On Nov 10, 2009, at 9:19 AM, Kulasekaran, Raja wrote:

> I'm using Apache::DBI and DBI->connect (persistence connection)=20
>=20
> So, Do I need to call $dbh->disconnect() for each child to close the
> connection ?

No, because Apache::DBI turns it into a no-op.

Apache::DBI is a very weird beast, with unanticipated
action-at-a-distance issues that crop up here and there. It's crazy
stuff like this that led me to abandon it -- at first for
DBI->connect_cached (though I had to do some extra work to make sure it
was safe), and more recently for DBIx::Connector, which does that extra
work for me.

Can you see what PIDs MySQL is accepting connections from? Are they the
same as currently-running Apache processes? Or are (some of them) from
dead Apache child processes?

Best,

David