Message text I said before that I think the "no winner" games are due to DB lock conflicts. In this case, it just threw a lock error, rather than timing out. Btw, it is probably not a good idea to dump SQL to the browser on an SQL error, as it could give a potential attacker clues how to approach your system.
Obsv SELECT UserID,Side,xPos,yPos,Heading,Stability,BArm,Carb,ObsFiredLastTurn FROM bm_PlaneStatus WHERE ObsStatus='Y' AND GameID=154242 AND InGame=1 uID:Ozvortex uSide:DE xp:3 yp:7 Head:4 SELECT xPos,yPos,Heading,Side,UserID,Stallo,PlaneID FROM bm_PlaneStatus WHERE GameID=154242 AND NOT(xPos=3 AND yPos=7) AND (((xPos Between 2 AND 9) AND (yPos Between 6 AND 7)) OR ((xPos Between 0 AND 7) AND (yPos Between 4 AND 5))) AND (Side<>'DE') AND (InGame=1)
============================================ Fine
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/play/bm_Common.asp, line 335
--- Message edited by ksnake
--- Message edited by ksnake |
|
|