Ah OK, if this is just a simple named lock then that is definitely a common thing. It sounded like you had a large number of locks that might be nested, etc., which might be an indicator that some other approach could be considered. Regardless, it's true that the memory tracking should not be locking (ha ha) things up like this. I wasn't making excuses for the Server Monitor, but rather just trying to see if there was an underlying issue that might need attention regardless of this apparent bug in the Monitor.
Regards, Brian On Fri, May 16, 2008 at 9:55 AM, Wim Lemmens <[EMAIL PROTECTED]> wrote: > @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:305410 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
