"Waldhoff, Rodney" <[EMAIL PROTECTED]> wrote: > This sounds a like an MSSQL issue, not a DBCP one--"MSSQL seems to close > connection in arbitrary moments"--does anyone know the logic by which MSSQL > wants to close connections? > > You don't experience similiar behavior without pooling? >
No, we don't. Sorry for the delay of my answer. Just want to let you know we've tested MSSQL 2000 with multiple user parallel without connection pool and we haven't got "Object has been closed" exception. Actually the MS JDBC driver implicitly contains connection pool and makes use of it. That's why it works quickly even without explicit connection pooling. Meanwhile Barney has found a reasonable cause for the connection time out problem. DBCP has a removeAbandonedTimeout setting that controls borrowed but not returned connections only... tele -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
