Running out of connection pool

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

Hi, I am using SqlHelper (Microsoft DAAB) library to perform database operation. But I have to came across 1 issue when I am getting exception with Connection pool that is full.

I have created basic Scenario for this exception

C#

public void method1(parameters)
{
SqlDataReader dr = null;
try{
dr =SqlHelper.ExecuteReader(CommandType,commandText);
if(dr.HasRows)
{
//Almost 7000 Records
while(dr.Read())
{
//Some Operation
Method2();
}
}
}
catch{}
finally
{
if(dr!= null)
dr.Close();
}
}

public void Method2()
{
SqlDataReader dr = null;
try{
dr =SqlHelper.ExecuteReader(CommandType,commandText);
if(dr.HasRows)
{
while(dr.Read())
{
// Only 1 Record
//Perform Some operation
}
}
}
catch{}
finally
{
if(dr!= null)
dr.Close();
}

using Above code my connection pool is full and not allow more connection Currently we allow 100 connection

Posted 18-Nov-14 7:23am

Jigar Sangoi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manas Bhardwaj · Answer 1 · 2014-11-18T08:00:00

That's for a reason that there are certain number of maximum connections available. If not, your code would end up consuming even more.

I don't see anything wrong in the code which you have provided here. However, if I make a guess it should be somewhere in your SQLHelper class which probably handles in the connection to SQL Server.

I would ask you check and make sure that the connection to SQL Server is properly closed.

See here how to close a connection:

http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.close(v=vs.110).aspx[^]