|
Hey there Tom -
Yes the intention here was to give the locks a unique name by using createUUID() - but as you have correctly pointed out the name as it stands will in fact be litereally "createUUID();" . I've changed the name to #createUUID()#.
Thanks :)
Paul
>>> [EMAIL PROTECTED] 30/10/2003 7:04:14 am >>> I just had my CFMX 6.1 server go bonkers on me for the second time in as
---many weeks. Both times the symptom was the same. It chokes on the lock name in "farcry_core/packages/farcry/versioning/sendObjectLive.cfm" and I've got to bounce the CFMX services. The lock(s) in question are named "createUUID();" That's a really unconventional lock name IMHO. Are you trying to create a new UUID for the lock name? I should also mention that there's a lock in "farcry_core/packages/farcry/versioning/rollbackarchive.cfm" with the same name. Haven't had any problems with that one, but then again. We almost never use rollback :) I understand the reasoning for the exclusive locks in those files, just not the names. What do you think, should we rename the locks or am I missing something here? ~Tom --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 |
- [farcry-dev] Re: Locking weirdness Paul Harrison
- [farcry-dev] Re: Locking weirdness Lucas Sherwood
- [farcry-dev] Re: Locking weirdness Paul Harrison
