On Monday 24 November 2003 03:35 pm, Perrin Harkins wrote:
> On Mon, 2003-11-24 at 15:11, Jordan Lederman wrote:
> > Honestly I don't yet know enough to tell you.
>
> You just have to look at the code you run from httpd.conf and startup.pl
> to see if it opens any connections. The code you posted looks fine, but
> what's in Q2::Init?
25 $Apache::DBI::DEBUG = 2;
26
27 my $dbh = DBI->connect("dbi:Pg:dbname=queue", "queued","",
{ AutoCommit=> 1, RaiseError => 1, PrintError
> 1 } ) or die "Cannot connect to db: $DBI::errstr \n";
I am a bit confused on why I need to connect to the db both in startup.pl and
in my module. Can you shed any light on this?
--jordan
>
> > If nothing useful is found here, i'll begin working on makeing the
> > problem happen in a smaller context.
>
> Yes, I'm afraid you do need to do that. You may find the problem by
> doing it.
>
> > > The restart command just sends a SIGHUP. That doesn't usually work
> > > perfectly with mod_perl. I always do a stop and start.
> >
> > I had thought that it was my fault. :)
>
> There's lots of discussion about this in the mail archives, if you
> search for SIGHUP or HUP. The gist of it is that you may leak memory
> this way, and the behavior with regard to what happens in the Perl
> interpreter is different in a DSO build and a static build. I always
> use static builds, no PerlFreshRestart, and cold stop/start, because it
> reduces the number of things that can go wrong.
>
> - Perrin
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
