The only reason that particular error would be appearing is if you actually
had >150 users hitting that server. ColdFusion has *no* control over how
many client are connecting. It *is* possible that you had some long-running
or server-locking CFM pages that causes clients to hang for an extended
period of time, and in that case the actual user queue ended up being
filled.
How 'heavy' is the CFML in your application? Have you considered moving the
maxclients over 150?
-jesse noller
-----Original Message-----
From: Devin Callaway [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 16, 2001 9:25 PM
To: CF-Linux
Subject: server reached MaxClients setting
Hi,
My server (soloris 2.8) running CF4.5.1 and apache 1.3.20 stopped
responding it has been up and stable for about a week. Apache and cold
fusion are both new to me. None of the cold fusion logs had anything in
them recent to the crash. The only thing i found was in the apache error
log was the following message.
server reached MaxClients setting, consider raising the MaxClients setting
Currently I have MaxClients set to 150
/etc/init.d/coldfusion stop && /etc/init.d/coldfusion fixed the problem.
So I am assuming that coldfusion had the clients tied up some how.
This may be more apache than it is cold fusion but since every page on my
site parses at least some cold fusion I have a hunch that coldfusion is
causing the problem.
Does anyone have any ideas what would cause this?
Also if anyone can tell me how to get more information about what is going
on other that the error logs I would greatly appreciate it.
Thanks in advance.
-devin-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
