On 3/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Whereas in my production environment, if I access some a new mod_perl page again and again over the course of a few minutes I'm almost guaranteed for users to trigger the error which actually occurs on _another_ mod_perl page which has been working okay since it's migration many months ago.
That's fine then. If you install some additional logging to trace requests based on PID, you can wait for the error and then go trace it back in your logs.
When you say 'good state' isn't it actually the job of mod_perl to reset the state of certain things?
We're getting into an area of total conjecture here, since I know almost nothing about the internals of taint mode. However, mod_perl doesn't generally try to clean up other people's messes.
I'm going to install Devel::Symdump so that I can use the Symbol Table part of Apache2::Status
That doesn't sound useful to me. What you want to know is the sequence of events. - Perrin
