Are you setting throwontimeout="true"? If you don't, and the lock times out, then the page will continue to execute, and stuff won't exist.
You might want to pay careful attention to how much code is inside of your exclusive locks. Leaving a lock open around database calls, or file I/O could leave those variables locked quite a bit of the time under high load. ~Brad -----Original Message----- From: Dave Phillips [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 1:19 PM To: CF-Talk Subject: Re: Problems with duplicate() in MX 6.1??? Well, apparently, this is not an issue with the duplicate() function. We took it out completely and just did a simple assignment. Apparently, there is an assumption that our <CFLOCK> above the assignment is timing out, and all variables are not getting set properly. This is why they aren't all duplicated into the request scope. We are going to try to figure it out this way now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257247 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
