Whelp, it used to work just dandy under mod_perl2 with the compat module. Not
sure why that has changed. I have confirmed that with mod_perl 2 it appears
to be very unhappy with the Apache libraries being referenced, although I'm
quite sure that didn't use to be the case.
Looks like I have
Peter von Weisz wrote:
Hi all,
Sorry for posting such a long compiler output.
This is on Scientific Linux (SL) 4.3 (a RedHat EL-based dist) with Apache
2.0.52 installed as an RPM. SL supplies a RPM called mod_perl-1.99_16-4
(which is installed), but that is not enough for the
I have written a handler that calls a constructor to a module that I
have written. I do not believe that the subsequent destructor is
being called unless I explicitly call it. Is this a feature of
mod_perl? I would think that every time an instance of the module is
created, it would be
I am not sure, but I think the problem you have is that Apache::DBI ignores
any disconnect() calls on database handles, and doesn't actually disconnect.
- Original Message -
From: Jordan McLain [EMAIL PROTECTED]
To: modperl@perl.apache.org
Sent: Tuesday, October 10, 2006 10:57 PM
I am not sure, but I think the problem you have is that Apache::DBI ignores
any disconnect() calls on database handles, and doesn't actually disconnect.
That's true.Apache::DBI ignores all the disconnect() calls.
--
Jeff Pang
NetEase AntiSpam Team
http://corp.netease.com
That is not the problem... The problem comes in when I do not use
Apache::DBI and I still end up with alot of mysql threads. The
problem is that I do not think DESTROY is being called.
On 10/10/06, Jordan McLain [EMAIL PROTECTED] wrote:
That is not the problem... The problem comes in when I
If I were you, I would put something like
warn I'm being destroyed.;
in the DESTROY method, so you'll know for sure whether that is the case.
- Original Message -
From: Jordan McLain [EMAIL PROTECTED]
To: modperl@perl.apache.org
Sent: Tuesday, October 10, 2006 11:20 PM
Subject: Re:
