Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Our IT Manager has brought up a situation where it looks like we have about 5000+ sleeping connections from the Crawl Server to our SQL Server. This seems like quite a bit and it's been slowly creeping up since our database server reboot a few weeks ago, after the machine was patched. So even if we reboot it looks like the connections will come back.

We are running SharePoint 2010 with the Search Service installed, the connections are all coming from the Crawler Server (we split up our Search Service to a few machines to separate the Crawler and Query services).

Anyone else seen this?

share|improve this question
add comment

2 Answers 2

up vote 0 down vote accepted

Since I've never been able to get a straight answer on this I am going to close this with - No Answer.

If anyone ever finds out why the connections that are supposed to be reused, are not, please let me know. Otherwise I don't want to leave this open.

share|improve this answer
add comment

Have you installed any third party solutions or custom solutions? If so you might not dispose of your SharePoint objects correctly. Each SPRequest-object (SPSite, etc.) creates its own data base connection. Try checking your ULS-Logs for any warnings about "undisposed requests".

share|improve this answer
    
The connections are all coming from the server that is used only for Crawling the site, there is nothing else there that would make a connection. –  MichaelF Aug 24 '11 at 15:53
    
well, you're right - nothing else makes a connection. But the crawler itself creates connections to the content, i.e. all content. Therefore SPRequest objects still get created. –  Robert Aug 26 '11 at 20:13
    
Ok, that I get. Should it generate that many without releasing them? Unless the Crawler is buggy I would expect it to release, or at the least reuse, those resources. –  MichaelF Aug 29 '11 at 13:10
    
Well, it should not, but with mistakes in programming, these resources might not be released. The problem does not reside on the crawler side, but on the SharePoint application side. For a in depth explanation, have a look at following article: blogs.technet.com/b/stefan_gossner/archive/2008/12/05/… –  Robert Aug 31 '11 at 21:34
    
Thanks, I have seen that but since this is the Search Service code how do I go about adjusting it? I've never seen anything that has shown how to make those changes. –  MichaelF Sep 1 '11 at 12:06
show 4 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.