The timeout period elapsed prior to obtaining a connection from the pool.

Question

0.00/5 (No votes)

See more:

System.InvalidOperationException: 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.
   at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)
   at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
   at Devart.Common.DbConnectionBase.Open()
   at Devart.Data.Oracle.OracleConnection.Open()
   at EasyCredit.Service.CustomerDetails.CustomerDetailsService.<SaveMailBodyForCasaVR>d__104.MoveNext()
--------------------------------------------------------------   at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)
   at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
   at Devart.Common.DbConnectionBase.Open()
   at Devart.Data.Oracle.OracleConnection.Open()
   at EasyCredit.Service.CustomerDetails.CustomerDetailsService.<SaveMailBodyForCasaVR>d__104.MoveNext()

What I have tried:

Getting this exception in the project. I have given 300 pool size in the web.config but still getting the exception of connection from the pool

Posted 15-Jan-20 3:31am

TanmoyDey

Updated 15-Jan-20 4:31am

Add a Solution

Comments

F-ES Sitecore 15-Jan-20 10:03am

If you don't have long-running processes, just make sure you are disposing of connections when you use them.

ZurdoDev 15-Jan-20 10:34am

What they said. ^

2 solutions

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)

Dave Kreskowiak · Accepted Answer · 2020-01-15T04:32:00

The most common cause of this is not properly disposing of connection object when you're done using them. The pattern for database use is to create and open as late as possible, do your database work, then close and dispose the connection as early as possible.

If you've got classes that open a connection for use anywhere in the class, this is a bad thing. Consumers of these classes typically don't call Dispose on them, and the classes themselves don't properly close and dispose of the connections, leaving them open for the lifetime of the class instance. When your instances go out of scope, this does not mean they have disposed of the resources they are using. They can hang around for quite some time, hogging resources, like database connections.

Patrice T · Accepted Answer · 2020-01-15T04:04:00

Solution 1

The error message tells you why your app crashed.
Now you have to add code to track what is going on in the pool.
I would log all pool requests and releases with time of operation and availability in pool.

Posted 15-Jan-20 4:04am

Patrice T