Thanks Perrin, I've been trying to use Apache::DB to track down the problem, but I'm not having a lot of luck.
I think it is in the locking as if I let things hang long enough and then shut down Apache, I get a error of: Can't call method "disconnect" on an undefined value at /usr/lib/perl5/site_perl/5.6.1/Apache/Session/Lock/MySQL.pm line 89 during global destruction. Which is Apache::Session::Lock:MySQL I'm still no closer as to figuring out why though. -Chris >> -----Original Message----- >> From: Perrin Harkins [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, February 19, 2003 11:55 AM >> To: Chris Faust >> Cc: Modperl >> Subject: Re: mod_perl 2 apache::session and "or die" >> >> >> Chris Faust wrote: >> > All works well except when there is any kind of problem in the >> script where >> > the condition will die.. >> [...] >> > When this happens everything to do with that script is >> unresponsive - I know >> > that is a little vague but that is the best way I can describe it. What >> > happens is the error comes up (standard server error) and that >> is the last >> > thing that is logged, if you try to go back and refresh the >> hourglass will >> > go for hours and nothing happens and nothing is ever logged >> >> It sounds like a locking problem to me. I'm guessing that mod_perl 2 is >> not calling the right hooks when it traps a die() to trigger the DESTROY >> method in Apache::Session which releases all locks. You can find out >> exactly what's going on if you run it in the debugger (Apache::DB) or >> throw some debug logging into Apache::Session to find out where it gets >> stuck. This is the beauty of having the source code. >> >> - Perrin >>
