DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36324>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36324 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-24 12:16 ------- Heya > I see that there's a 3rd party module in the call stack. It's hard to know > whether the data structure corruption is coming from the 3rd party module or > from within Apache. It's our own module. Naturally this is suspect! :) I have tried to find things in it that could cause this, but haven't been successful. Sadly we can't run in production without that particular module so testing with it unloaded is impossible. > I realize this is on production machines so this might not > be possible, but if you could enable pool debugging and bucket debugging in a > build at least long enough to repro the problem, that would be very helpful in > tracking down the source of the corruption. We are quite happy to run one machine with those on (is bucket debugging a seperate configure option to --enable-pool-debug?). However, the occurence of the runaway child processes is so low (say 3-4 over 12 machines in 3 weeks) that we could run for weeks without reproducing it. I'm loath to try something that will be very hard to draw a conclusion from (has it actually solved it, or have we simply not hit the problem yet). Additionally, it's worth noting that when we turned on pool debugging to investigate bug 35974 the problem there (which happens a handful of times a day) disappeared. The only idea I came up from looking at other bugs was whether our problems are down to the lifetime of data created in subrequests - and that perhaps this is different under a pool debug build (we tried the patch in bug 12655 without success). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
