It's less a CF issue, and more about a traffic and simultaneous reads/writes. Make good use of WITH NOLOCK on database reads where you can. It's not always a single record that is locking. Depending on how your tables are indexed and a variety of other factors, a page (SQL page) could be locked, or the whole table could be locked -- just for a read.
Also, the users shouldn't be seeing that error at all, right? (site-wide error handler...) Cheers, Kris This is less about getting a specific answer and more about just finding out > how to diagnose the problem. Client has an ColdFusion application in a > multi-server instance behind a hardware load balancer. The ColdFusion server > are on separate machines but talk to the same MS-SQL db. > > Within the last few days users have started to see ColdFusion errors saying > that: > > "[Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 102) > was deadlocked on lock resources with another process and has been chosen as > the deadlock victim. Rerun the transaction." > > Any clues what this might be in regards to? How do I go about trying to > track this down? And does this have anything to do with the multi-server > setup or is it just a more vanilla problem with an update occurring slowly > with the server? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326542 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
