It's important to first understand the nature of a deadlock. Let's say you have the following two chunks of code anywhere in your app:
CFLOCK session.myVar1 and read session.myVar2 inside the lock CFLOCK session.myVar2 and read session.myVar1 inside the lock If these two chunks of code are ever executed by different threads at the same time you have a deadlock because each lock is waiting for the other to finish. Look through your code and make sure you don't have any issues like this one Bryan Love -----Original Message----- From: Justin Waldrip [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 10:10 AM To: CF-Talk Subject: Deadlock Your transaction (process ID #39) was deadlocked with another process and has been chosen as the deadlock victim. Rerun your transaction. I am receiving quite a few of these errors in a row. Where is a good place to start looking for things that might cause this? Thanks, Justin ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
