On Tue, Sep 21, 2010 at 12:09 PM, Sharon Pattison wrote:
> We added some logging to several of our scripts to log when $r->args and
> $q->query_string do not match. What we find for the bad process is that $r
> always has the correct data for the new request, but the value of
> $q->query_string n
Hi,
I think I sent my last reply just to Tuomo, so am sending again to the
list..
Thanks for the suggestion. I checked our error logs and did not find that
message anywhere.
We added some logging to several of our scripts to log when $r->args and
$q->query_string do not match. What we find
Are you getting "variable will not stay shared" messages in your error_log?
If you are, you might be using a lexical variable outside of the function
it was defined in. When this happens, you'll get a closure, which is a
useful tool sometimes, but for us regular people it means that old data
will
[ please reply-all to keep it on the list ]
On Mon, Sep 20, 2010 at 4:07 PM, Sharon Pattison wrote:
> We would still like to track down the cause of the problem, if we can. The
> process does indeed seem to become broken at a particular point and the CGI
> object has an incorrect query_string fo
Hi,
> After adding a lot of logging to our logs, we discovered that the Apache
> request object will have the correct information, but the CGI object never
> seems to get the global values reset, so is always has the query_string of
> the request where things started to go wrong. The process will
Hi,
We are experiencing a strange problem on our web servers for our site, and
are not sure if the problem is mod_perl related, but thought we would turn
here for help in case someone else has experienced this issue.
Unfortunately, we are not sure exactly when the problem started, so we can’t
poi
