Hi there
I had some problems using the DBCP connection pool with 4.1.6 and the MS SQL Server JDBC drivers. I couldn't get the pool to use the user parameter specified in server.xml, I ended up having to include the username and password as part of the JDBC URL.
Oh, I've never used the built-in connection pooling before, so I can't speak for 4.1.3. What's happening with your 4.1.6 setup??
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 3:10 AM
To: Tomcat Users List
Subject: Re: Tomcat-4.1.6 and DBCP issue?
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.
It is easy to replace the DBCP included with another version or a new
nightly if there is a problem (just replace commons-dbcp.jar in common/lib).
In the case of 4.1.6, some last minute changes were integrated in DBCP,
so maybe there was some regression.
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
