I'll take a look at the spider thing. As for Queued threads, I guess my fundamental question (Which you alluded to) Was whether incoming queued requests are stored as threads.
Also, is there any harm in my pages if I throw the URL inside the thread name? This might help me understand when things are being processed, etc... as I already convert the thread list to a cfquery... If I do java.lang.Thread.currentThread().setName(hostname+path_info etc...) I can further narrow down page requests and who's handling them... Thanks -dov >Are you watching the cfstat utility when you see this? I've seen >similar things happen when the configured active thread count reaches >it's max due to a lock or long running thread and threads start >queueing. Then the log-jam breaks and the threads decrease rapidly as >the queue empties out. > >If you watch cfstat, you'll see the running thread count = the max set >in your cfadmin, then you'll see the queued requests race upwards. >This type of behavior is particularly common in apps that typically >handle alot of very small/quick requests, but occasionally run into a >longer running process. > >-Cameron > > >On Mon, 27 Dec 2004 15:05:04 -0500, Katz, Dov B (IT) ><[EMAIL PROTECTED]> wrote: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - RUWebby http://www.ruwebby.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188834 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
