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??
DBCP expects the user to be identified by a parameter called "username",
not "user" :-)
To unsubscribe, e-mail: <mailto:tomc...@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomc...@jakarta.apache.org>