Hi,
Since we moved to Aolserver 4.5.1, we've been getting alot of these on our
logs: 'Notice: exiting: exceeded max connections per thread'. Does that mean
that Aolserver is receiving more connections than it can handle? If so, what
would you recommend us do? Our servers are running on Debian
Someone wiser than me may correct me on this but I believe this is just a
notice message.
Each thread can handle 126 connections ([expr $threads_maxthreads * 7]) after
which the thread will get destroyed. This is historically done to make sure
any memory leak doesn't take over the machine,
The code that each connection thread runs to service a connection is wrapped
within a while loop that starts at whatever you set ns/threads - maxconns to
and counts down to zero. When it reaches 0, a connection thread exits. If
ns/threads - maxconns is set to 0, then your connection threads
Hi there,
Is there any wisdom in this community about whether it's better to let
these threads run forever, or whether it makes more sense to kill them
off after they process a number of connections?
Thanks,
Haig
On 2/15/2011 2:18 PM, Scott Goodwin wrote:
The code that each connection
Haig Didizian wrote:
Hi there,
Is there any wisdom in this community about whether it's better to let
these threads run forever, or whether it makes more sense to kill them
off after they process a number of connections?
As others mentioned, the downside of letting a thread run forever is
Hi,
Is there a way of killing the threads once max connection has been reached
or does aolserver automatically take care of this?
Regards
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
lists...@listserv.aol.com with the
body of SIGNOFF
I would recommend killing them, just in case there is some memory leak or other
glitch which causes problems.
For example, I had an issue with threads when I used a filter to process
requests, the filter would use ns_adp_parse to parse an adp which would either
fill the buffer with HTML or
The server does it for you.
Date: Tue, 15 Feb 2011 14:53:34 -0800
From: thejackschm...@gmail.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded max connections per
thread' mean?
To: AOLSERVER@LISTSERV.AOL.COM
Hi,
Is there a way of killing the threads once max connection has been reached
From my own experience, it seems that I get a ton of that like all the
threads (or a majority of them) have exceeded max connections and it seems
that it does take a while before they start serving again. I'd like to know
if this is normal or should the turn around time be a lot quicker...
If you have a lot of .tcl files then it will take longer for the new threads to
be created (so if you are using OpenACS then it can take awhile depending on
the RAM and CPU power of your server)
Increase the connections per thread to 1000 and see how that works for you.
There is (in theory)
The thread exiting code is based on maxconns and
timeout. If e.g. maxconns is is very low (e.g. 20),
the default spread of 20 does not make a lot of change.
Furthermore it is more important, when many
connection threads are configured (e.g. 80), and the there
is much library code (e.g. fully
11 matches
Mail list logo
