That's not the only situation where you get deadlocks. On Friday we were discussing that, and the problem then was due to page locks in MSSQL. The deadlocks in CGLOBAL are at row level, and I see now what that has to do with the mixing client variables. People probably sent out URLs with their CFID and CFTOKEN on them. So whoever followed the link while the session was alive shared the same session! So possibly we had different browsers/computers/clients causing updates for the same row in CGLOBAL at the same time. For the CGLOBAL problem, we'll just disable the updates. For the mixing variables problem, I'll look at what Rob says...
Thanks :) Claudia -----Original Message----- From: Bryan Love [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 1:24 PM To: CF-Talk Subject: RE: deadlocks in CFGLOBAL Strange. Deadlocks most often happen when you have code that updates one row in the DB based on info from another row. Example: UPDATE cellGlobal SET myVar = (SELECT myVar from cellGlobal WHERE foo = 1) WHERE foo = 2; This code is dangerous because it could cause deadlocks... what if it's updating row 1 based on row 2 while a concurrent thread is updating row 2 based on row 1? deadlock Search your code for any client variable updates that might cause the above situation to happen. +-----------------------------------------------+ Bryan Love Macromedia Certified Professional Internet Application Developer Database Analyst Telecommunication Systems [EMAIL PROTECTED] +-----------------------------------------------+ "...'If there must be trouble, let it be in my day, that my child may have peace'..." - Thomas Paine, The American Crisis -----Original Message----- From: Hoag, Claudia (LNG) [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 9:02 AM To: CF-Talk Subject: deadlocks in CFGLOBAL Does anyone know why I get row level deadlocks in CFGLOBAL and what are the implications of that? The other day I talked to our DBA about some deadlocks (not related to CFGLOBAL) and she started to look for them... And found a whole bunch of deadlocks in the CFGLOBAL table. Those are row level locks and if she didn't start looking for them, I would never take notice that those were happening. I wonder if that has anything to do with users complaining that their client variables are getting mixed with other users' client variables. I can't see how that would happen, considering that the client variables rely on a cookie set for an individual browser... Any ideas? TIA, Claudia ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
