Microsoft Knowledge Base Email Alertz

KBAlertz.com: FIX: Error message when a System.Data thread tries to open a pooled connection in the .NET Framework 2.0: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 948868 - Last Review: April 2, 2008 - Revision: 1.0

FIX: Error message when a "System.Data" thread tries to open a pooled connection in the .NET Framework 2.0: "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool"

On This Page

SYMPTOMS

Consider the following scenario. In the Microsoft .NET Framework 2.0, a System.Data thread tries to open a pooled connection. At the same time, another thread tries to clear that pool by using the ClearPool method or the ClearAllPools method. In this scenario, you receive the following error message:
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.
This problem occurs in the following versions of the .NET Framework 2.0:
  • The release version of the .NET Framework 2.0
  • The .NET Framework 2.0 Service Pack 1

CAUSE

This problem occurs because of a race condition in the internal call of the GetConnection method. After both the connection pool group and the connection pool are obtained, the GetConnection method is called on the pool. If the ClearPool method is called between the GetConnectionPool method and the GetConnection method, the pool state is changed to ShuttingDown, and the GetConnection method returns the null value. These things occur because of the race condition. Then, because the null value is interpreted as a time-out, you receive the error message that is mentioned in the "Symptoms" section.

RESOLUTION

Hotfix information

To resolve this problem, install the hotfix that is mentioned in the following article in the Microsoft Knowledge Base:
948815  (http://kbalertz.com/Feedback.aspx?kbNumber=948815/ ) Availability of the .NET Framework 2.0 post-Service Pack 1 hotfix rollup package for System.Data.dll and System.Data.OracleClient.dll

Prerequisites

You must have the .NET Framework 2.0 Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
The .NET Framework 2.0, x86 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.18132,998,27204-Feb-200820:49x86
System.data.oracleclient.dll2.0.50727.1813484,35204-Feb-200820:49x86
The .NET Framework 2.0, x64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.18132,998,27204-Feb-200820:49x86
System.data.oracleclient.dll2.0.50727.1813484,35204-Feb-200820:49x86
System.data.dll2.0.50727.18103,113,47214-Jan-200815:36x64
System.data.oracleclient.dll2.0.50727.1810499,71214-Jan-200815:36x64
The .NET Framework 2.0, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.18132,998,27204-Feb-200820:49x86
System.data.oracleclient.dll2.0.50727.1813484,35204-Feb-200820:49x86
System.data.dll2.0.50727.18133,208,19204-Feb-200817:25IA-64
System.data.oracleclient.dll2.0.50727.1813503,80804-Feb-200817:25IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Call stack information

System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
System.Data.SqlClient.SqlConnection.Open()

APPLIES TO
  • Microsoft .NET Framework 2.0
Keywords: 
kbexpertiseadvanced kbpubtypekc kbqfe kbhotfixserver KB948868
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please