Devart Forums

Hello,

We are currently using OreDirect.Net (ver 3.55.25.0 and 3.55.18.0) for our application (ASP.NET 1.1 to Oracle 10g).

It seems that there's a limited number of connections in the connection pool that OraDirect can handle, when it gets over twenty(20) connections, all the connections are blocked/invalidated, no exception raise, and application hangs.

We did try to set the "Max Pool Size" down to 5, and it's handling the connections ok, and on the 6th session was throwing out and expected error below:

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.

We then increased the Max Pool size one by one and again error was properly handled as expected (as above), until the "Max pool size" gone over 20, all the connections were blocked and application hang.

Is this a bug in OraDirect or is there a configuration setting that we need to set to get over this default value of 20.

Has anybody encounterred a similar issue, and what action need to be taken to rectify this problem.

Thanks and regards

Hung Truong

To solve the problem increase value of the Max Pool Size connection string parameter. The default value is 100.
Another way to get extra connections is to clear one or all of the pools. Or you can turn connection pooling off using Pooling connection string parameter.
It is also possible that the server settings limit acceptable connections.

If all said above didn't help please send us a small test project.