@Brian It's clear that the locking is not the issue here, so I don't think there's much reason to elaborate on that. The problem is that a running process is blocked at a random point inside a lock (when the Memory Tracking is activated). This causes the lock to be active for ever (beyond the lock timeout), which prevents other requests from obtaining the lock. We are using named locks, so it doesn't really block the application, but just that particular process. However, this behavior is seen in all processes (for various named locks), so in practice, the whole application is blocked.
Stopping the Memory Tracking solves the issue. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:305409 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
