Re: accept mutex failure causes fork bomb

2009-09-15 Thread Jeff Trawick
On Mon, Sep 14, 2009 at 4:27 PM, Greg Ames ames.g...@gmail.com wrote: I'm trying to debug a problem where apparently the accept mutex went bad on a z/OS system running the worker MPM. I'm guessing that some memory that we use for the semaphore got clobbered but don't have proof yet. The

Re: accept mutex failure causes fork bomb

2009-09-15 Thread Jeff Trawick
On Mon, Sep 14, 2009 at 4:27 PM, Greg Ames ames.g...@gmail.com wrote: * Should we yank the squatting logic? I think it is doing us more harm than good. IIRC it was put in to make the server respond faster when the workload is spikey. It finally occurred to me what you meant by spikey:

Re: accept mutex failure causes fork bomb

2009-09-15 Thread Greg Ames
On Tue, Sep 15, 2009 at 8:07 AM, Jeff Trawick traw...@gmail.com wrote: On Mon, Sep 14, 2009 at 4:27 PM, Greg Ames ames.g...@gmail.com wrote: I'm trying to debug a problem where apparently the accept mutex went bad on a z/OS system running the worker MPM. I'm guessing that some memory that

accept mutex failure causes fork bomb

2009-09-14 Thread Greg Ames
I'm trying to debug a problem where apparently the accept mutex went bad on a z/OS system running the worker MPM. I'm guessing that some memory that we use for the semaphore got clobbered but don't have proof yet. The error log looks like: [Mon Sep 07 08:01:59 2009] [emerg] (121)EDC5121I