I've discovered what I think is the cause for the connection timeout is in DBCP and MSSQL.
In Poolman there is an elememnt: <connectionTimeout> The connection will be destroyed after living for this many seconds. DEFAULT: 1200 seconds (20 minutes) (I have this set to 10mins, and never see connection timeouts....) This appears to be why PoolMan works but DBCP gives timeouts. Poolman automatically closes and recreates connections after a certain period whereas DBCP simply leaves connections open. So I'm guessing implementing you're own custom object pool with a timeout should solve your problem too Tele. I'm going to stick with Poolman until I get around to upgrading Tomcat. I'll try and write and submit a patch to fix this problem when I get time. Hamish > -----Original Message----- > From: Barney Hamish [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 30, 2002 11:06 AM > To: 'Jakarta Commons Users List' > Subject: RE: [DBCP]: Connection closed on MSSQL 6.5 > > > I've been using PoolMan for over a year and never had this > occur... But I'm > nor sure how to go about working out what the difference > between the way the > two systems implement pooling.... Does anyone know why this > would occur with > DBCP and not with PoolMan? > Hamish > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
