"news.microsoft.com" <molund@oroad.com> wrote in message
news:OeKzPeBREHA.568@TK2MSFTNGP12.phx.gbl...
> Is there an elegant way to clear out the ADO connection pool used by the
SQL
> Server State Service following a cluster failover?
>
> We are using a SQL Cluster to store both the ASP Session State database
and
> our application database.
>
> When the SQL Server cluster is failed-over, any "pointers" to the live
> connections stored in the connection pool are made invalid. When the
> application tries to reference these "damaged" connections, it throws an
> exception, and the pooling mechanism drops the bad connections from the
> pool.
>
> In our application, we are using a looping try/catch block to clear out
the
> bad connections from the pool following a failover, and the users
typically
> are not affected by the failover as a result of any exceptions in our
> application code.
>
> However, we don't have access to the source code for managing the ASPState
> connections. It appears as though there is no mechanism for the ASPState
> database to clear out the bad connections from the pool following a
> failover, and thus the exceptions are affecting users.
>
> Is SQL Server Session State Management even supposed to work with a SQL
> Cluster?
>
> Mike Olund
> OpenRoad Communications
>
>

"news.microsoft.com" <molund@oroad.com> wrote in message
news:OeKzPeBREHA.568@TK2MSFTNGP12.phx.gbl...
> Is there an elegant way to clear out the ADO connection pool used by the
SQL
> Server State Service following a cluster failover?
>
> We are using a SQL Cluster to store both the ASP Session State database
and
> our application database.
>
> When the SQL Server cluster is failed-over, any "pointers" to the live
> connections stored in the connection pool are made invalid. When the
> application tries to reference these "damaged" connections, it throws an
> exception, and the pooling mechanism drops the bad connections from the
> pool.
>
> In our application, we are using a looping try/catch block to clear out
the
> bad connections from the pool following a failover, and the users
typically
> are not affected by the failover as a result of any exceptions in our
> application code.
>
> However, we don't have access to the source code for managing the ASPState
> connections. It appears as though there is no mechanism for the ASPState
> database to clear out the bad connections from the pool following a
> failover, and thus the exceptions are affecting users.
>
> Is SQL Server Session State Management even supposed to work with a SQL
> Cluster?
>
> Mike Olund
> OpenRoad Communications
>
>