Re: Closing DB handler with PerlCleanupHandler

[prev] [thread] [next] [Date index for 2004/11/10]

Hi Perrin,

> It looks to me like you are creating this problem by using "our".  Why
> 
> not use "my" and pass the handle around, or put it somewhere like 
> $r->pnotes() instead?

Yes I should have used 'my' and passed the handle around :(

> Also, why do you want to avoid persistent connections?

Because the DB is running out of memory just to keep the persistent
connections, I just want to try it without persistent connections and
see the result. If the overhead is not too big, I might just change it
to use normal connections.

I tried this to disconnect the handler in PerlCleanupHandler, but it
didn't work.

## httpd.conf
<FilesMatch "\.pl$">
  SetHandler perl-script
  PerlResponseHandler ModPerl::Registry
  PerlOptions +ParseHeaders
  PerlCleanupHandler MyApache::Cleanup
  Options +ExecCGI
</FilesMatch>


## MyApache::Cleanup.pm
package MyApache::Cleanup;
use strict;
sub handler {
    my ($r) = @_;
    our $dbh;
    if ($dbh) {
        print STDERR "Got ya!!";
        $dbh->disconnect();
    }
    return 200;
}
1;

I can't get $dbh from module that is called by PerlCleanupHandler. $dbh
is created by scripts in ModPerl::Registry. How can I disconnect 'our
$dbh' created by scripts within ModPerl::Registry in PerlCleanupHandler?

Regards,
--bk


        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html