Hi Dossy, You said that current should never drop below min. But in my case after threads have serviced configured number of requests they start to die. idle and current keeps dropping until 0 and never comes up again.
The server logs shows lines like: [01/Oct/2007:16:41:43][20634.3027639200][-conn:335-] Notice: exiting: exceeded max connections per thread [01/Oct/2007:16:42:19][20634.3027499936][-conn:336-] Notice: exiting: exceeded max connections per thread [01/Oct/2007:16:42:37][20634.3027360672][-conn:337-] Notice: exiting: exceeded max connections per thread It looks like as threads begin to die after servicing 150 requests no new threads are created. nspool output at the start of the server: nspools=minthreads 400 maxthreads 500 idle 400 current 400 maxconns 150 queued 11 timeout 60 nspools output showing when idle and current are at 1: nspools=minthreads 400 maxthreads 500 idle 1 current 1 maxconns 150 queued 56,679 timeout 60 Can anyone point out what i'm going wrong here. Why the new threads are not being created in the pool? kind regards, On 9/15/07, Dossy Shiobara <[EMAIL PROTECTED]> wrote: > > > Both current and idle, when server is started their value is set from > config > > file. e.g. if i set min to 100 then the current and ilde has 100. But at > > that point there's no request why does current returns 100? > > current indicates the current number of threads in the pool. Current > should never drop below min and never exceed max. If current == idle, > then all threads are idle. If idle == 0, then all current threads are > busy servicing a request. > > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
