Re: Io exception ORA-17002 via JDBC

I get the same error from a JDBC 1.2.x applet downloaded over a dial-up connection from my server connected to the internet over an ADSL connection when the applet tries to connect using the thin driver.

It works fine on the intranet.

Does anyone know if there's a work-around.

Thanks

Chi

David Wall wrote:

> In an application in which the client running with JDBC connects to Oracle
> 8.1.7 over the Internet, the underlying socket appears to be reset from time
> to time.
>
> In JDBC, it raises and SQLException with an error code set to 17002.
> However, the Connection object itself is not closed by the JDBC library.
> This is unfortunate because if the connection in error were closed, it would
> be easy to detect the failed connection (as opposed to any of the myriad
> other SQL exceptions that can arise). Most connection pools I've seen
> attempt to check if the connection is closed before handing them out, so if
> it is, it can recreate the connection.
>
> How are others handling this situation? I hate to have to call a method
> every place where SQLException is thrown and have it be checked in a
> non-portable way to see if the exception itself affects the connection or
> not, and if so closes it.
>
> Thanks for your insights...
>
> David
>
>
>
Received on Thu Nov 21 2002 - 08:13:38 CST