in reply to Re: mod_perl go boom, mod_cgi works
in thread mod_perl go boom, mod_cgi works

"Another is to reduce the number of requests each Apache child can handle before exiting, thus exiting before the accumulation of problem memory chunks to the point of a crash."

This idea strikes me in two ways...

  1. The code or running application is not freeing memory or globals at each iteration...
  2. This is just a workaround for badly-written code that is incorrectly using globals or some other shared structures.

That being said, I've limited MaxRequestsPerChild in Apache to 2, and so far, I am not able to reproduce the problem. I'm not confident this "solved" the problem however...

One thing I did notice though, was that when I'm clicking through my sample feeds linked from the front page of this mod_perl application, sometimes my click for 'foo.bar.xml' will report that 'example.com.rdf' does not exist. example.com.rdf is a feed I might have clicked last, or 10 clicks ago. It seems random, but leads me to believe there is some persistence going on here. A clue?

Is there a more detailed way to find out if I'm using globals somewhere, that my old eyes can't see?