OK, I removed the path and docBase attributes from the Context element;
as expected, the warning in the log goes away but the DataSource problem
does not.
The mysql-connector-java-5.1.5-bin.jar file is world-readable; it is in
$TOMCAT_HOME/lib and nowhere else; I did have another copy in
$TOMCAT_HOME/common/lib per a suggestion in a different thread, but that
made no difference so I removed it.
- Thomas
Caldarale, Charles R wrote:
From: Thomas Okken [mailto:[EMAIL PROTECTED]
Subject: Re: DataSource created but not initialized = Cannot
create JDBCdriver of class '' for connect URL 'null'
There is a warning about the docBase attribute (strange; I
copied that text verbatim from the Tomcat FAQ); if I remove
that attribute, the warning goes away, but the DataSource
remains uninitialized.
The FAQ is out of date for 5.5 and later levels.
You should also remove the path attribute, since it's illegal when the
Context element is not in server.xml (and such elements should never
be in server.xml).
The docBase attribute is illegal unless the app is located somewhere
outside of the Host's appBase directory.
However, neither of the above is causing your DB connection problem.
Have you checked permissions on the mysql-connector-java-5.1.5-bin.jar
to make sure Tomcat can read it?
Does that jar (or any MySQL jar) also exist in the webapp's WEB-INF/lib
directory? If so, remove it; it shouldn't be in two places at once.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
