On Tue, 2004-05-18 at 17:36, Dave Boodman wrote: > By regular do you mean with each invocation?
I mean that it happens frequently enough that it's not likely to be tied to some freak occurrence involving race conditions or other inter-process issues. > Cause I regularly see the same children not return the newly-inserted > data, while (most) others regularly return it fine. So that means that there is something which puts them in a bad state and then they can't recover. > In -X, the single process always returns the right data. How are you testing? And how are you testing when you run it without -X? You probably are running a different sequence when you test without -X, since your requests are all randomly split up between apache children. > 66218 2004-05-18/14:32:53 64.186.244.42 debug dave Plugin::Systems 33 > retrieve(col00179) returning 3 hashes > 66247 2004-05-18/14:32:53 64.186.244.42 debug dave Plugin::Systems 33 > retrieve(col00179) returning 1 hashes > 66267 2004-05-18/14:32:54 64.186.244.42 debug dave Plugin::Systems 33 > retrieve(col00179) returning 2 hashes > 66217 2004-05-18/14:32:54 64.186.244.42 debug dave Plugin::Systems 33 > retrieve(col00179) returning 1 hashes > > (where each call/reload should be retrieving 3 hashes) I don't know what these log statements mean, since they are not in the code you're showing. I'd suggest you try replacing your Lib::System call with a call to something really simple and see if the error goes away. When you take something out and the error is gone, you know that piece was at least a part of the problem. > Is it possible mysql children are feeding httpd children bogus data? It's very unlikely that this is a MySQL problem. Many people run MySQL and don't report this problem. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
