I have a program that looks for remote SQL Servers and pulls
information off of them every x minutes.
It's possible that the DSL connection to one of the servers can be
down for an extended period of time. If that happens, I have good
exception handling and logging so that it doesn't try to pull data off
of that server.
I'm experiencing a problem when a server is down for some period of
time, but then comes back up. The problem is that the application
immediately fails after trying to open the connection, like it doesn't
even try to open it.
If I stop and restart my program (it's a .NET program running as a
Windows service), then it detects that the server is back up and
starts working.
One other note - if I change a config file so that the server name is
the IP address of the server, OR from IP address back to server name,
then the program detects that the server is back up and starts pulling
data again. (meaning - I change connection string to something else
and the program detects the server is back up).
Could this be some sort of connection pooling issue? I need my program
to detect when the server comes back up and start pulling data without
manual intervention.
matt tag