><cflock name="#session.st#ProcessLock" timeout="20" type="exclusive"> > >I'm taking a bit of a guess here, but I think your name may be the problem. >I'm assuming that by having a session variable in the name, each user will >have a different name for the lock. Named locks are only locked from >blocks with the same name. If each user is getting a unique name, then the >block will not be locked between users. That is my understanding of locks >at least. > >If this is the case, you want a single, discreet name for the lock so that >all users use the same named lock and thus can only use the block of code >one at a time, which I believe is your requirement.
The fact that the lock is given a name based upon a session variable is definitely a problem--that only guarantees that the locked code won't run for sessions where the variable "session.st" is identical. I'm guessing that variable is unique per session. Also, just because you lock code calling the ReqNumbering.cfc component, the code in that component is not necessarily locked. That means if RegNumbering.cfc is called from other places outside of this "locked" code, it would run unlocked. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:295018 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
