Hello Remy, Cool, that did it! Just by replacing the 4.1.6 version of commons-dbcp.jar with the 4.1.3 version made everything work again.
I guess this definitely means a regression was introduced into commons-dbcp in 4.1.6. Jake Tuesday, July 02, 2002, 2:09:40 AM, you wrote: RM> Jacob Kjome wrote: >> Hi, >> >> I'm just checking to confirm whether others that used DBCP connection >> pooling successfully in Tomcat-4.1.3 are running into problems when >> using Tomcat-4.1.6? That is the case for me. I'll check again >> tomorrow to see if I did anything stupid, but the only difference seems >> to be the tomcat version, so it would follow that something broke in >> DBCP between 4.1.3 and 4.1.6. RM> It is easy to replace the DBCP included with another version or a new RM> nightly if there is a problem (just replace commons-dbcp.jar in common/lib). RM> In the case of 4.1.6, some last minute changes were integrated in DBCP, RM> so maybe there was some regression. RM> Remy RM> -- RM> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> RM> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Best regards, Jacob mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
