.
Date: Tue, 15 Feb 2011 15:17:08 -0800
From: thejackschm...@gmail.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded max connections
per thread' mean?
To: AOLSERVER@LISTSERV.AOL.COM
From my own experience, it seems that I get a ton of that like all
the threads (or a majority of them) have
, 15 Feb 2011 15:17:08 -0800
From: thejackschm...@gmail.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded
max connections per thread' mean?
To: AOLSERVER@LISTSERV.AOL.COM
From my own experience, it seems that I get a ton of
that like all the threads (or a majority of them) have
exceeded
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
and is being destroyed.
Date: Tue, 15 Feb 2011 22:49:05 +0800
From: tapsitu...@gmail.com
Subject: [AOLSERVER] What does 'exiting: exceeded max connections per thread'
mean?
To: AOLSERVER@LISTSERV.AOL.COM
Hi,
Since we moved to Aolserver 4.5.1, we've been getting alot of these on our
logs: 'Notice
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
that you are always destroying and creating threads.
Date: Tue, 15 Feb 2011 17:20:27 -0500
From: h...@wineaccess.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded max connections per
thread' mean?
To: AOLSERVER@LISTSERV.AOL.COM
Hi there,
Is there any wisdom
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...
...@gmail.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded max connections per
thread' mean?
To: AOLSERVER@LISTSERV.AOL.COM
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
speak to varying the number of connections per thread.
Date: Tue, 15 Feb 2011 15:17:08 -0800
From: thejackschm...@gmail.com
Subject: Re: [AOLSERVER] What does 'exiting: exceeded max
connections per thread' mean?
To: AOLSERVER
13 matches
Mail list logo
