Hi David, a) you may want to use 'timeout' property in the connection URL, or as data source property, depending on how you create your connections.
b) If you are not inside a transaction (you are either in autocommit mode or have just executed a 'commit' or 'rollback') the driver reconnects silently (if not told otherwise with the reconnect property) c) when handing out a connection from your pool to your application, checking whether it is open using the 'isClosed()' method is a good idea to detect sad things (i.e. database is offline) at a central point. Regards Alexander Schr�der SAP DB, SAP Labs Berlin > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 03, 2003 7:01 PM > To: [EMAIL PROTECTED] > Subject: JDBC and timeout > > > > Hi, > > I have our own set of "pooled" connections - we create 25 > when we start up, > and share them between clients. > > Just wanted to check that all I have to do is add the > database param to my > init file: > > param_put SESSION_TIMEOUT 0 > > to avoid these jdbc connections timing out? ie there is > nothing on the driver side I need to set? > > Many thanks, > > David > > > > _______________________________________________ > 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
