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.
Jake -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
