I want to know how commons DBCP would cope with DB connections that have gone idle and are closed by the
database.
I've used commons DBCP provided by tomcat and find that after 15 minutes SAPDB will close the connection.
When DBCP gives the webapp a connection, we get a BorrowObject null and throw a exception. I've found that
writing some sort of keep alive helps this alot for us.
Does anyone know if the nightly build of DBCP can cope with this better ?
Thanks.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
