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).
Just + info... Maybe your connection pool library implements one like this... []s Edson Richter ----- Original Message ----- From: "Sven K�hler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, June 03, 2003 8:43 PM Subject: Re: JDBC and timeout > What do you suggest? Isn't this a common solution in a pooling situation? I implemented a pool, that stores as many connections as possible, but only for let's say 60 seconds. If there is high demand, there can be many connections in the pool, if there is low demand, the pool-size will shrink. Of course, one could limit the maximum number of connection, and set a minimum size. I always check with "isClosed()" if a connection is still alive before i return it to the caller. A fixed-sized pool is not what i would call a good idea. _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.487 / Virus Database: 286 - Release Date: 1/6/2003 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
