Remy,
I reported bug 10614 for this issue against the commons project.
However, I thought that you might want to look at it as well since it
might also be a Tomcat/commons integration issue. I posted a stack
trace in that bug. Can you take a look and let me know what you think
the problem
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
Title: RE: Tomcat-4.1.6 and DBCP issue?
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
Douglas, Rory wrote:
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.
Title: RE: Tomcat-4.1.6 and DBCP issue?
Thanks Martin, that worked!
The problem is that the TC-4.1.6 Admin web-app adds a user ,not a username parameter when you add a DataSource resource.
-Original Message-
From: Martin Jacobson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02
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
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
