Weird. The whole point of Apache::DBI (or so I understand it) is so that
your $dbh stays valid across CGI or Handler calls.
I can only think of two reasons why I get the error message:
1) My child process is dying, and the DBI code is telling me that I never
called disconnect() on that $dbh. I don't think this is the case, since the
line (#119) in Apache::DBI that is referenced in the error is in the
connect() call.
2) My $dbh has timed out, and Apache::DBI is attempting to reconnect. The
code author decided not to perform a disconnect() because they knew the
connection was already timed out.
I'm assuming that it's #2, but wanted to find out if other folks had seen
this as well, since I don't normally see much in the error_log.
-jse
> From: Tom Mornini <[EMAIL PROTECTED]>
> Date: Mon, 24 Apr 2000 22:42:49 -0700 (PDT)
> To: "John S. Evans" <[EMAIL PROTECTED]>
> Cc: modperl <[EMAIL PROTECTED]>
> Subject: Re: Apache::DBI disconnect?
>
> On Mon, 24 Apr 2000, John S. Evans wrote:
>
>> Dang. That "delete" code is in the Apache::DBI code (Apache/DBI.pm line
>> 119). Is this a known bug in Apache::DBI, then?
>
> No, I don't know of any problems with Apache::DBI. Typically the error
> message that you are talking about happens when your $dbh goes
> out-of-scope without an explicit disconnect.
>
> Are you disconnecting in your code?
>
> --
> -- Tom Mornini
> -- InfoMania Printing and Prepress
>
