I've been monitoring this issue for a while since we first had the problem, and I wanted to bring it back up and ask if there is any new progress on allowing us to modify the connection pool settings. I want to reiterate that I have NEVER used an application with a database connection pool that doesn't know how to recover from a temporary loss of database connectivity by automatically dropping closed connections from the pool. We just restarted the database on our production server, and all of our applications handled it just fine, except Sitefinity, which required us to go out and touch the web.config file to force a reload (See attached screenshot of the error).
Might seem like a trivial problem that won't happen under normal conditions, but this will make the difference between me sleeping peacefully through the night, or waking up to login and restart the website after the DBA reboots the database server. In addition it will result in a significantly larger amount of downtime while nobody knows that connectivity has been lost until it's reported by an end user.
Waiting for the application to go idle and recover on it's own is not feasible, as it won't go to sleep if there are constant requests coming in. Can you give me any other solution to this problem?