Hi Folks, I wonder if someone can help me.
I have a situation where I use cflock when generating IDs to ensure no duplications occur etc which 'sometimes' results in a deadlock situation. <cflock timeout="8" throwontimeout="No" name="LockName" type="EXCLUSIVE"> <cfset ID=..........> </cflock> <Insert Query Here> Because the Throw is 'no' whenever the lock gets 'stuck' for whatever reason (which is quite rare, but has a high impact negative outcome) the timeout is ignored and then it carries on forever, or atleast until I restart my webserver. It is important to keep the Throw set to No. Does anybody have any suggestions as to what to do to break this vicious circle of locking without any manual intevention? The code above is actually an improved snippet than my earlier version because I had previously included a select query and an insert query inside the same bounding CFLOCK by the way. This may have been the root cause of my problems because there was more work required in the original lock code, but I don't really understand cflocks enough to be sure. Maybe I could use an server monitor software to analyse a test CF page which tries to run a lock with the same name and then runs some sort of action to restart on it's own as a last resort? Thanks a lot Andrew ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:313389 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
