Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tracking Down what is causing a Locked thread

Status
Not open for further replies.

Kalisto

Programmer
Feb 18, 2003
997
GB
SqlEnterprise Manager Version 8 (if it makes any difference)

I have a sporadic issue where all my applications that rely on the Sql Database fail, and report errors along the lines of ""

I have poked around in Enterprise manager but I cant see any obvious way of finding out what has caused this to happen.
By the time I get there and look at the Current Activity / Locks, there are a large number of icons, but nothing obviously flagged up as locked. (Scrolling through them all again does not reveal what has caused the issue)

I suspect that one of the applications has not closed a connection, but I dont know how to prove it.

Is there any way of finding out more information about who has not released a lock, or how long a lock is being kept open for?

As an additionl question, I have gone through the log files as well, and there are many entries for "Login Failed for user 'sa'"

All our databases have their own explicit password / usernames, so is this anythign I need to worry about (other than the fact that something is trying to access the default account on the database)

K
 
What's the error that your applications are reporting? It didn't get put into the post.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog
 
Sorry :$
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
 
That's probably a problem with .NET running out of pooled connections. How many connections are there at that time, and how large is the pool?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog
 
This is the problem, there are multiple applications running.

By poking about some more I think I have found out where the locks are, and 3 particular sprocs in one database are detailed in there again and again. Double clicking on them just gives me sproc name, then a ;1 but Im going to talk to the person responsible for that bit of code and see if we can investigate frther. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top