Tomcat's database pooling implements a slightly refactored version of
the Commons DBCP project -- packages were renamed to avoid conflicts
should a developer decide to use the Commons DBCP library in their own
app. You can find a complete list of possible attributes for the
Resource definition
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Re: Datasource: Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver'
>
> type="javax.sql.DataSource"
> maxActive="100" maxIdle="30" m
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Re: Datasource: Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver'
>
> BUT: It is running and yet my META-INF/context.xml
> still contains the path and docBase attributes.
In your case, they are probably b
Chuck,
Thanks. As Dave pointed out, my core difficulty was a permissions problem.
BUT: It is running and yet my
META-INF/context.xml
still contains the path and docBase attributes.
Where can I read up on what should be in META-INF/context.xml ??
RE:
By intercepting and discarding the orig
David,
Bingo! Right on: Changed all permissions (chown -R tomcat myapp), and
dropped the mysql jar from WEB-INF/lib, and
it all works. Many thanks! I do hate it when I forget simple stuff
like permissions. Moving things from Windows to *nix
always does that to me.
Side note question: Am
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Datasource: Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver'
>
> MyApp AppListener: ENTER
> DAOBaseData: Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver'
By intercepting and discarding the original except
Don't 'copy' the mysql driver from WEB-INF/lib to TOMCAT_HOME/common/lib
-- move it. It cannot be in both places at once. Also be sure the
permissions are set correctly so tomcat can read the jar and be sure
you've restarted tomcat after the move so the classloaders pick it up
properly. I ha
