Hello, I have different experience... The isClose()-Method do not check if the connection is down. It still returns true, also if the Database Manager shows no sessions anymore. In my experience isClose() returns true, if an "Timeout-Exception" has occured, or close() will be called before. By the way, this is the descibed behaviour from the JDBC Spec.
regards, Kolja -----Ursprungliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Sven Koehler Gesendet: Mittwoch, 4. Juni 2003 17:29 An: [EMAIL PROTECTED] Betreff: Re: JDBC and timeout > Several Pooling tools provide a configuration option like "ValidationQuery" > that will be issued to guarantee that the connection still valid (check, as > example, Apache Jakarta Catalina 4.1 DBCP Connection pooling). As far es i know, the isClosed() already does some kind of "pinging" the kernel (at least in the SAPDB JDBC driver). _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
