>>are you willing to sell your tool that fixed it? we are adding more of
these servers and will need some sort of fix...<<
I'm not willing to call it a fix... It's more like a very dodgy band-aid
over a high-pressure leak.
Essentially, it's a perl script that monitors the server.log file for the
word semaphore. When it sees it, it restarts ColdFusion. The problem is that
ColdFusion does not write log entries immediately, there can be up to a
couple minutes delay.
I'll see about getting the details to you tomorrow.
Michael J. Sheldon
http://www.desertraven.com/
Make a fast friend, adopt a greyhound!
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 03, 2001 16:09
To: CF-Linux
Subject: Re: RE: CF Error
High odds make winning bets..
here is my server.log entries:
Warning","TID=5868577","01/03/01","18:23:40"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=5870627","01/03/01","18:23:42"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=5871652","01/03/01","18:23:44"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=5873704","01/03/01","18:23:45"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=5872679","01/03/01","18:23:45"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=5880881","01/03/01","18:23:54"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Error","TID=5899318","01/03/01","18:24:12","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=5949466","01/03/01","18:25:15","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=5960741","01/03/01","18:25:30","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=5966863","01/03/01","18:25:34","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=5967888","01/03/01","18:25:34","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=6011921","01/03/01","18:26:53","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=6025230","01/03/01","18:27:04","Unable to write reply -- client
browser stopped waiting for request. "
"Warning","TID=6285349","01/03/01","18:33:13"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6284324","01/03/01","18:33:13"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6286347","01/03/01","18:33:14"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6287373","01/03/01","18:33:15"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6288422","01/03/01","18:33:16"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6289447","01/03/01","18:33:17"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6290472","01/03/01","18:33:18"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6291497","01/03/01","18:33:19"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6292492","01/03/01","18:33:24"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6293518","01/03/01","18:33:24"," Timed out while waiting for
thread semaphore (5 requests are active)"
"Warning","TID=6294543","01/03/01","18:33:25"," Timed out while waiting for
thread semaphore (5 requests are active)"
are you willing to sell your tool that fixed it? we are adding more of these
servers and will need some sort of fix...
are there any ports to FreeBSD planned?
thanks.
jc
>I'll give high odds you'll see semaphore errors in your CF logs.
>
>Generally, this means that all of CF's processing slots (Limit simultaneous
>requests to X in the administrator) were busy long enough to cause a
request
>to time out before it could even start getting processed.
>Counter-intuitively, increasing this may only make the problem worse.
>
>In our case, whenever we see this happen, the CF server never recovers, all
>subsequent requests will get this error until we reset ColdFusion. We had
to
>write custom routines to monitor the logs and restart ColdFusion
>automatically. (The restart at X unresposive requests setting in the
>administrator *never* works in this case)
>
>Michael J. Sheldon
>http://www.desertraven.com/
>Make a fast friend, adopt a greyhound!
>
>
>-----Original Message-----
>From: Jon Cline [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, January 03, 2001 22:24
>To: CF-Linux
>Subject: CF Error
>
>
>Has anyone received this error before? We are only receiving about 6
>requests / second on our RedHat 6.2 Linux Box.
>
>What could be causing this? Apache can serve greater than 120 requests /
>second.
>
>
>
>
>Error Occurred While Processing Request
>Error Diagnostic Information
>Timeout waiting for request to execute
>
>The server is unable to fulfill your request due to extremely high traffic.
>Please attempt your request again (if you are repeatedly unsuccessful you
>should notify the site
>administrator).
>
>I have CF 4.5.1 SP2 for RedHat Installed.
>
>thanks.
>
>jon cline
>enthusiast, inc.
>[EMAIL PROTECTED]
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.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.
