At 10:42 AM -0800 3/16/99, Eric Hermanson wrote:
> I know this topic has been discussed in the past, but there never has been a
> satisfactory solution, as far as I can tell. The problem occurs when using
> the ODBC adaptor to connect to MSSQL Server. If the database server resides
> on a separate machine, and that machine is rebooted unexpectedly, the
> WebObjects application connected to that server then raises a "Communication
> Link Failure" exception whenever data is fetched.
>
> The ways around this seem to be numerous, the safest of which may be to
> handle the exception at the highest level and simply terminate/restart the
> application. But in this instance I don't have access to Monitor which will
> restart it for me, so I would like to force the Adaptor to reset the
> database connection. Is this a possibility? Would it be as simple as
> checking for a closed channel, calling openChannel if necessary? Or would
> the adaptor be in some other type of wierd state where the channel is still
> open, but the connection is just plain hosed (and unrecoverable)?
>
> - Eric
Someone claimed once that the source to the ODBC adaptor was available,
so you could change it to have whatever behavior you want. However, I
don't think there's any good solution to this problem since its not
clear how you would recover from this in all cases. Really, this
pretty much hoses the EOAdaptor since it would have no way of
synchronizing between the object store and the database store
reliably.
Maybe you could write an ExceptionHandler for the exception to
cause the Application object to kill all running sessions, and reset
all the EOAdaptors.
Pierce
----------------------------------------------------------------
Pierce T. Wetter III, Director, Twin Forces, Inc.
e-mail: [EMAIL PROTECTED] Phone:520-779-4227
<http://www.twinforces.com/>
U.S. Mail: 1300 South Milton Rd, Suite 206, Flagstaff, AZ 86001
