Ive been trying to isolate some CF lockups that we have been receiving since I rolled out a new application. The new app uses CFOBJECT to call a custom COM which I believe is the culprit. Im curious on the following settings:
Limit simultaneous requests: 5 Ive always had this set to 5 and seemed to work well prior to the new app being rolled out. Restart at 10 unresponsive requests: I guess this is actually defaulting to 5. It appears my COM is stalling (based on server.log). Usually when the unresponsive thread count reaches 2-3 I need to manually stop and restart CF, then all is ok. Sometimes I see that CF restarts itself (Unresponsive thread threshold reached. Restarting Service). When CF restarts itself it appears to be transparent as I dont receive the "Server is busy blah blah" message as when I manually stop/start CF, is this true?. Until I can resolve my COM problem is it recommended to set the unresponsive requests to say 2, what would a recommended setting for this be.? Additionally, if I receive the "A request exceeded the timeout. The unresponsive thread count is up to 1." message, do I now only have 4 possible threads to process under or is the stalled thread released? When I receive the "A request exceeded the timeout. The unresponsive thread count is up to 1." message, this it is not logged in the application.log and I dont receive an error, it just appears to be a runaway task. If this is the case would it be useless to wrap the process in a CFTRY/CATCH module? This all running on CF4.01 Thanks,Adrian ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
