CF doesn't kill threads that take longer than this value - most of the time
it can't (for example if it's given control of that thread to an ODBC
driver). It simply updates the "lost thread count" by one.
Once the thread comes back it drops the count. If the count ever reaches
the number of lost threads setting you specify in the administrator then CF
will reboot itself.
If you're seeing messages like this you should track down which
templates/requests are taking so long (using "log slow pages" is a good
start). If they're rare and eventually come back (the unresponsive thread
count is reduced) then I wouldn't worry too much about it (but it's still
worth looking at) but if they're common then they indicate some serious
performance issues someplace.
Jim Davis
_____
From: Marlon Moyer [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 1:29 PM
To: CF-Talk
Subject: Unresponsive threads
I've been researching my logs and I'm finding a lot of lines like such:
A request exceeded the timeout. The unresponsive thread count is up to 1
My question is how long is the timeout for a thread to be considered
unresponsive?
--
marlon
"And Bobby you are right, I am being selfish, but the last time I checked,
we don't have a whole lot of songs that feature the cowbell!"
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
