Connection Pooling Problems
386549Jan 28 2003 — edited Jan 31 2003Hi everyone,
I am running into a problem with opening connections with ODP .NET. It seems that no matter what my connection string is, the timeout value remains at 15 seconds or so. In fact, it seems that my connection string parameters are ignored entirely.
For a test program, I have created multiple threads, have each thread create a new connection and attempt to open it. I'm then sleeping for 7 seconds to simulate some usage time for the connection then closing it.
I can change min pool size, max pool size, etc etc and never see different behavior when opening the connections. Usually when it has opened about 50 connections (despite max pool size being set to 10), trying to open connections starts timing out on me (despite having the timeout set to 500).
I'm not sure what is going on, but if we have several connections performing lengthy operations, I can't have the connection.Open() calls timing out on me after only 15 seconds. Trying to catch the problem and reopen seems like a nasty workaround for something that is supposed to be part of the pooling mechanism.
My connection string looks like:
"Data Source=GTD4;User ID=****;Password=****;Min Pool Size=5;Max Pool Size=10;Connection Lifetime=0;Connection Timeout=500;Pooling=true"
These aren't necessarily the sizes I will want in production. I was just setting them to various values to try to see what was going on. I've changed them to many different values and see no change in program behavior.
Any ideas?