Unnamed Connection Pool in ADO.NET
In our database view we are seeing "unnamed connection pool" along with our other named connection pools. This is a .net ado.net application. What does "unnamed connection pool" mean? ADO.NET uses the connection string to name the connection pool. If connection string is null or empty, there would be no database to connect to.... yet, there are transactions going across the unnamed pool.
Thoughts?
The upcoming Fall Release will fix some of the issues we had with unnamed connection pools. Would be great if you could test it out once 5.6 is available and let us know whether it solves your problem
Hi Andreas
We're using 4.2. but it seems to have recovered the name and is displaying properly again.
Regards
Gregor
I'm having exactly this problem, did you ever get this resolved ? Oddly it was recognising the connection pool up until recently.
Thanks
Gregor
Hi Bill
We identify Connection Pools based on the actual ADO.NET Provider Implementation (SQLServer, Oracle, ...) as well as the information from the Connection String. It is possible that you use a ADO.NET PRovider that we do not know - is that possible?
In any case - could you export a PurePath and send it to us? either attach it to this post or send it to my via email
Andi
