I think I just found the bug. Reading source code can be fun! :)
Seems the MySQL backend was having the problems. Restarting it cleared
up the errors. I'm not sure if there's something about Apache::DBI
aggrevating the daemon or not (I don't need to pursue this further
right now), but it's wor
Alex Menendez <[EMAIL PROTECTED]> wrote:
>this destroy routine is definitely a problem (may or may not be the cause
>of the error though) apache::dbi over-rides the dbi connect method in
>order to check an internal hash of cached db handles so that an existing
>connection can be returned rather th
this destroy routine is definitely a problem (may or may not be the cause
of the error though) apache::dbi over-rides the dbi connect method in
order to check an internal hash of cached db handles so that an existing
connection can be returned rather than taking the performance hit of
establishing
I am completely confused...
I have a couple of connections I use - one for general information,
another for authentication purposes. I am wanting to use Apache::DBI
to cache the connections.
When running as httpd -X I have no problems whatsoever. However,
running as normal, it will work fine
