Joost N wrote:
Our website gets hundreds of hits per minute on busy times and has
been happily running mod_perl for about 4 years now, without any
problem, so I suspect it has something to do with the upgrade earlier
that day.
It's a logical conclusion, but I doubt it. I can't think of anything
that changed between releases of 1.x that could cause this sort of bug.
I suspect the bug has been there all along but only happens in
specific circumstances.
Could there be a problem that the output buffer of a previous request
is not flushed completely (due to a broken connection perhaps), so
that part of the output gets sent to the next client of the same
process?
I don't think so.
This kind of thing is usually caused by a scoping bug, where something
is getting put into a global or a closure and unintentionally used on
consecutive requests. It could also be caused by multiple people
getting the same session ID, depending on what you use to generate them.
If you describe what you upgraded from and tell us something about how
you manage sessions, we might be able to make better guesses.
- Perrin
