Hi,
I've got a question about the "Verify Connection" connection string property.
When I set this property to true in my connection string always get exceptions saying "Trying to put a closed connection to pool".
When I look into the documentation, I see that it should check the connection when it is obtained from the pool.
The moment when the exceptions are thrown seems quite odd to me, since my application might return closed connections to the pool (hence, faulted connections). However, I assumed that the pool would not complain about this and instead make sure that there are "Min Pool Size" open connections available.
What is the original idea behind the current implementation?
Or did I just run into a bug?
Regards,
Ruud
"Verify Connection" connection string property
-
- Devart Team
- Posts: 2420
- Joined: Wed 02 Nov 2011 09:44
Did you mean ValidateConnection property?bozr wrote:I've got a question about the "Verify Connection" connection string property.
We could not reproduce the issue with 'ValidateConnection=true'. If it is possible, create and send us a small test project with DDL/DML scripts for reproducing the issue.