Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: Deadlock on ML7_0_2x Only in Debug

  1. 02-02-2011, 09:01 AM #1
    Garf is offline Senior Member
    Join Date
    May 2006
    Posts
    190

    Default Deadlock on ML7_0_2x Only in Debug

    Hi there

    Looking at a clients website and I am getting a lot of deadlocks when trying to run in debug.

    It's always in the SessionGetByID but there is no unlocked selects in that statement. Anyone know of the culprit as it's getting a little annoying and a little concerning that something might come back to haunt me when the changes go live.

    Cheers in advance
  2. 02-03-2011, 08:40 AM #2
    deanfp is offline Senior Member
    Join Date
    May 2009
    Location
    Sweden
    Posts
    556

    Default

    Is there a deadlock graph in the Error Log?
  3. 02-04-2011, 03:41 AM #3
    Garf is offline Senior Member
    Join Date
    May 2006
    Posts
    190

    Default

    Found it.
    GetSessionByID had a select without a NoLock.