January 6, 2012 at 8:33 am
We have a 3.5 .NET application running with three 2005 Enterprise SQL Servers set up with mirroring (active, mirror, and witness). We have been running our application without issue for several years on IIS 6.0; automated database failover from primary to secondary, or failback from secondary to primary worked without issue. We recently upgraded to IIS 7; the application is no longer failing over in a reasonable time period if the database fails over from primary to secondary (it will after a couple hours or a manual restart of the application within IIS). However, automatic failback from the secondary to primary database server is still working well.
Has anyone else experienced this? Can it be addressed with settings in IIS 7, or does it require updates to the database connection code in the application? Any help is appreciated!
Thanks,
Kevin
January 6, 2012 at 8:57 am
I'm not sure this is something new with iis7 but recently we had some problem with some application when failover occured.
This was due to a not explicit enough error given by the connexion pool (via ADO.NET). It just tells that the connexion cannot be reused but not the reason.
So your application has to try each connexion from the pool before really creating a new one.
The new one will use the mirror server.
If your application finally fail over after a few minutes, this could be ypur problem. And if so, Try to modify the way you handle the connection opening and to catch errors when opening fail and implement a retry system
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply