About 12 months ago we cured our instance of CF5 of this problem but suddenly it's back.
About once a day CF gets very unresponsive for about 30min or so. A large number of response timeout errors happen during that period, and then it goes away. Everything else on the box runs fine and is responsive. The CF processes are not gobbling memory or CPU cycles and the overall load on the box is minimal. During these episodes CF starts and stops fast but goes back to being unresponsive immediately on start up. We have applied the fixes to client variable storage to stop the registry bloating from that source. Is it possible that the registry has grown to critical mass from the 24 datasources we have registered? Should we not register them, but have each application provide the connection info? Why does this happen daily for a definite period. Is there some daily background task (clean up or rereading the registry, for instance) that causes this until it's done that task? adTHANKSvance, Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm?link=i:14:3327 Archives: http://www.houseoffusion.com/lists.cfm?link=t:14 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:14 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
