The timeout period elapsed prior to obtaining a connection...

[Guest]

Hi,

I have recieved the following error in an application:

"Timeout expired. The timeout period elapsed prior to obtaining a
connection from the pool. This may have occured because all pooled
connections were in use and max pool size has been reached".

I think it may be masking another error but have been unable to replicate it
in our test environment. I don't think pooling is an issue because the
connection string is common to many components and only one particular
transaction out of hundreds possible is causing the problem. I have checked
the event logs and the only problem that occured at roughly the same time as
the latest failure was a "System.OverflowException: Value was either too
large or too small for an Int32."

Has anyone come across a situation where the pooling exception was covering
up something different?

 

[Marc Gravell]

Does the operation in question do anything in a loop? If it isn't
closing connections (back to the pool) then this could still cause
this problem. Have you tried monitoting the connection-count at the
dbms to see if it spikes? Since it *suggests* pooling, it is worth
taking a few moments to just investigate if the error is correct.
Depending the the dbms, MARS might help a little (but this is a band-
aid, not a solution).

But no, I haven't seen this /particular/ type of cover up, but yes:
sometimes exceptions are highly misleading ;-p

Marc

 

[Guest]

Thanks marc,

I ran the transaction through SQL Profiler and while other transactions make
a single call then reset the connection, this made 40 calls between resets.
I will investigate further......