That's true. My assumption on that topic is that the thread goes to sleep while it waits for the "third party call" and a thread has to be running to notice if it has timed out. That's because there is _not_ a second thread spawned to watch the first one, but instead the thread asks "am I timed out" over and over while it is running. I've seen it in thread dumps before.
It's kind of annoying, but if I am correct-- it does make a little sense. ~Brad -----Original Message----- From: Matthew Williams [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 12, 2007 9:53 PM To: CF-Talk Subject: Re: clustering issue In addition to that, you might want to check out Sarge's blog and do some jrun.xml tuning. The problem with relying on CF to time out requests is that it doesn't work for third party calls. So, what's a third party call, you might ask? Would you think that DB connections would count as third party calls? I wouldn't, but it turns out they are. Most of our hosted apps use Oracle stored procedures. If the DB goes down, or becomes unresponsive, those calls back up in a hurry. Most of my FusionReactor termination activity comes from time outs associated with DB calls that don't ever complete. Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:294701 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
