| Erik Anderson 2005-06-21, 8:23 pm |
| Is there an ODBC client timeout setting anywhere available? This would
allow the client to return with an error message when attempting to connect
to an ASA server that is present but for some reason nonfunctional, as an
alternative to having it wait indefinately until the server is
administratively closed (using either sharedMemory or tcpip).
I am not attempting to diagnose the reasons that caused the server to become
nonfunctional in the first place (there are a number of causes, many of
which have been resolved or created over the years), and these situations
have come up for one reason or other the whole time I have been working with
ASA as a product. (i.e. this is not tied to a "version or build" of ASA)
I guess I'm just a bit frustrated at going in to diagnose scheduled events
that have not been running and have not been giving errors only to find 16
instances of them showing up in the task manager, all stuck on CONNECT
operations that never succeed. This is not a situation I know how to have
my client application detect, other than potenitally through a watchdog
thread that hopefully allows enough time for CONNECT operations to succeed
before calling Abort() on itself.
|