> PH> Another solution is to have the child process exit if the ping
> PH> fails. You get one failed request, but you clear out the messed
> PH> up processes quickly and replace them with new ones that can
> PH> connect safely.
>
> Yeah, good point. Although our poor little WAP ser
> "PH" == Perrin Harkins <[EMAIL PROTECTED]> writes:
PH> Are you loading the Oracle driver in the parent process (with
PH> startup.pl)? I think I remember this sometimes causing problems
PH> with re-connecting.
No, but we did hand load it in a module called from perl.conf with
Pe
> Apache::DBI's ping check worked fine, but when the dbh was ejected from
> the cache (and so went out of scope), something in the DESTROY stack
> was blocking, and holding the child up for 12m. I'm guesing the
> underlying DBD::Oracle code was trying to do a nice shutdown on the
> dbh, but o
