Re: Variant of Monday-morning bug with Apache::DBI + DBD::Oracle
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 obviously couldn't. Quick hack: Tweak Apache::DBI to keep the ejected dbh in scope, in a global @array or something, and perform a daily/weekly restart on apache. Are you loading the Oracle driver in the parent process (with startup.pl)? I think I remember this sometimes causing problems with re-connecting. Another solution is to have the child process exit if the ping fails. You get one failed request, but you clear out the messed up processes quickly and replace them with new ones that can connect safely. - Perrin
Re: Variant of Monday-morning bug with Apache::DBI + DBD::Oracle
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 PerlModule. We had a good reason for that, too (to do with the Oracle driver overloading alarm(), so that the second alarm in alarm(20); $dbh = DBI-connect(dbi:Oracle:..., ...); alarm(0); cleared a different type of alarm that the first call set ...) 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 service (for that is what was for) gets so few hits, they'll all be getting failed if we do that ; - Adam
Re: Variant of Monday-morning bug with Apache::DBI + DBD::Oracle
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 service (for that is what was for) gets so few hits, they'll all be getting failed if we do that ; Okay, try never letting the connections go idle. Set up a cron to send in a request every minute or so, or whatever it takes to keep your Oracle connections active. - Perrin
