MENU LOGIN 
   Redirecting... ...to our OLD website!


We're still in the process of converting the site to the new format.

Apologies for the inconvenience and thank you for your understanding.

-Matt, Admin

5

Ok - go now to OLD site

No thanks - stay on NEW site


BM Website Issues/Help Requests

URGENT: Site errors - deadlock victim

URGENT: Site errors - deadlock victim (4) - Forums [Biker Match] URGENT: Site errors - deadlock victim (4) - Forums [Biker Match]
Home / Search Forums / BM Website Issues/Help Requests /

URGENT: Site errors - deadlock victim

 Posts: 121       Pages: 4/7

Post Reply
yep - that line updates the view count for the topic your in. It therefore locks the database for a split second. I think I may have found the root cause of everything though now. Large searches of profiles are taking 15+ seconds now that we have so many members. The main cause of this is the sheer amount of postcodes it's searching through (And comparing against profiles). When someone runs a search, it locks the database for that time period! Hence nobody else can then get in (i.e. to open the forums, etc) To try and work towards a fix now, i'm going to change the scripts so that you CANT search for any more than 50 miles. We can all monitor it over the weekend and see if we still get the error.

   Update Reply
Matt @ 09/08/2007 15:08  

Matt just got this: Microsoft OLE DB Provider for SQL Server error '80040e31' Timeout expired /sites/bm/header_inc.asp, line 143

   Update Reply
cbrbabe @ 09/08/2007 15:12  

that updates the last time you were active. You got in there before i fixed the problems though. :-) Try from now on. PS: Does a 50 mile radius limit bother anybody in the searches? Surely 50 miles is a lot? Just until I find a solution

   Update Reply
Matt @ 09/08/2007 16:01  

50 mile limit ok temporarily it doesn't affect ME cos I aint searching but think it good to have nationwide choice too, for OTHERS

   Update Reply
Sandi @ 10/08/2007 00:14  

nationwide is easy to do, because it means simply no narrowing down, I can add that tonight. The problem is when searching, say 200 miles, because that means that 2000+ postcodes have to be filtered through against the profiles. Each postcode takes time to filter. 50 miles searches in about 2 seconds which is ok. Nationwide will be QUICKER because I wont have to filter the profiles at all :-) Leave it with me

   Update Reply
Matt @ 10/08/2007 03:06  

Just got this one Matt at 17.38ish! Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 91) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 67

   Update Reply
Di @ 10/08/2007 13:41  

and this one at 17.41!!!! Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 85) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/posts.asp, line 199

   Update Reply
Di @ 10/08/2007 13:42  

offs!!!!!!!!!!!!!!!!!!!!!!! 17.44 Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 135) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 187

   Update Reply
Di @ 10/08/2007 13:44  

thomsondiane aka 'Deadlock Di' lol

   Update Reply
Sandi @ 10/08/2007 13:51  

Jesus, you're just TRYING to break the site!!! Will pass the info on.

   Update Reply
Matt @ 10/08/2007 13:53  

arrrrrrrrrrrrrrrrggggggggggggghh!!! 17.54 Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 135) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 187

   Update Reply
Di @ 10/08/2007 13:59  

What the hell u doing woman? lol Give me 5, im downloading the logs now

   Update Reply
Matt @ 10/08/2007 14:09  

Damn I got it now... Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 133) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 125 19:20 on 10th August

   Update Reply
Matt @ 10/08/2007 14:20  

Ha ha smarty pants

   Update Reply
Di @ 10/08/2007 15:09  

Whats it like now? Running smooth again? Site seems fast for me at the moment

   Update Reply
Matt @ 10/08/2007 17:34  

Its been faster since ya last said it was, Matt, and not many error messages, but when they do happen the site goes sluggish

   Update Reply
Sandi @ 10/08/2007 17:50  

yea, i think it was being caused by big searches (People searching 100+ mile radius). It locks the site temporarily. Never used to notice because there werent so many people using the site at once.

   Update Reply
Matt @ 11/08/2007 08:08  

Well aint that typical of folks registering to use the site, just not cricket what?! lol

   Update Reply
Sandi @ 11/08/2007 17:20  

Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/chat/Usersdata.asp, line 13 just got this at 21:20

   Update Reply
fjr_graham @ 11/08/2007 17:20  

Look wot I just got Matt @ 22.12 Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 148) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 125

   Update Reply
Di @ 11/08/2007 18:15  

 Posts: 121       Pages: 4/7

Back to top
Facebook Twitter Google Pinterest Text Email