You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jesse Keller <je...@aya.yale.edu> on 2003/04/08 18:20:16 UTC
Re: Basic JNDI setup problems - "Cannot load JDBC driver class'null'"
Thanks, Paul. In my non-dbcp test servlet, I use
Class.forName("org.gjt.mm.mysql.Driver").newInstance();
with good results, so I don't think that's the problem. Is it possible that
because it's a Windows system, the slashes in the path are confusing Tomcat?
C:\> echo %CATALINA_HOME%
C:\Program Files\Apache Group\Tomcat 4.1
C:\> cd %CATALINA_HOME%/common/lib
C:\Program Files\Apache Group\Tomcat 4.1> -- windows doesn't see the
slashed path
C:\>dir "C:\Program Files\Apache Group\Tomcat 4.1\common\lib\mysql*"
Directory of C:\Program Files\Apache Group\Tomcat 4.1\common\lib
02/17/2003 12:17p 211,470
mysql-connector-java-3.0.6-stable-bin.jar
----- Original Message -----
From: "paul niemandt" <ma...@acesurfer.co.za>
To: <to...@jakarta.apache.org>
Sent: Tuesday, April 08, 2003 11:56 AM
Subject: Re: Basic JNDI setup problems - "Cannot load JDBC driver
class'null'"
> Either your mysql driver is not in $CATALINA_HOME/common/lib or you are
> using the wrong class name: try com.mysql.jdbc.Driver in stead of the
> mm.mysql thingy.
>
> [my guess, anyways]
>
> regards,
> Paul
>
> On Tue, 2003-04-08 at 16:42, Jesse Keller wrote:
> > I've seen lots of posts about this error message, but none of the posted
solutions seemed to apply. I'm running Tomcat 4.1 with MySQL connector/J
3.0.6 on Win2000. I can connect to the database OK from a servlet without
dbcp, but when I try to use dbcp, it dies:
> >
> > Context ctx = new InitialContext();
> > DataSource ds =(DataSource)ctx.lookup("java:comp/env/jdbc/TestDB");
> > Connection conn = ds.getConnection();
> >
> > ctx.lookup() returns a non-null object. So far, so good. But
getConnection() throws java.sql.SQLException "Cannot load JDBC driver class
'null'"
> >
> > Thanks in advance for any help!
> >
> > Here's the relevant part of my server.xml:
> >
> > <!-- this stuff added to support dbcp -->
> >
> > <Context path="/DBTest2" docBase="DBTest2"
> > debug="5" reloadable="true" crossContext="true">
> >
> > <Logger className="org.apache.catalina.logger.FileLogger"
> > prefix="localhost_DBTest2_log." suffix=".txt"
> > timestamp="true"/>
> >
> > <Resource name="jdbc/TestDB"
> > auth="Container"
> > type="javax.sql.DataSource"/>
> >
> > <ResourceParams name="jdbc/TestDB">
> >
> > <parameter>
> > <name>factory</name>
> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
> > </parameter>
> >
> > <!-- Maximum number of dB connections in pool. Make sure you
> > configure your mysqld max_connections large enough to handle
> > all of your db connections. Set to 0 for no limit.
> > -->
> > <parameter>
> > <name>maxActive</name>
> > <value>5</value>
> > </parameter>
> >
> > <!-- Maximum number of idle dB connections to retain in pool.
> > Set to 0 for no limit.
> > -->
> > <parameter>
> > <name>maxIdle</name>
> > <value>3</value>
> > </parameter>
> >
> > <!-- Maximum time to wait for a dB connection to become available
> > in ms, in this example 10 seconds. An Exception is thrown if
> > this timeout is exceeded. Set to -1 to wait indefinitely.
> > -->
> > <parameter>
> > <name>maxWait</name>
> > <value>10000</value>
> > </parameter>
> >
> > <!-- MySQL dB username and password for dB connections -->
> > <parameter>
> > <name>username</name>
> > <value>root</value>
> > </parameter>
> > <parameter>
> > <name>password</name>
> > <value>newpass</value>
> > </parameter>
> >
> > <!-- Class name for mm.mysql JDBC driver -->
> > <parameter>
> > <name>driverClassName</name>
> > <value>org.gjt.mm.mysql.Driver</value>
> > </parameter>
> >
> > <!-- The JDBC connection url for connecting to your MySQL dB.
> > The autoReconnect=true argument to the url makes sure that the
> > mm.mysql JDBC Driver will automatically reconnect if mysqld
closed the
> > connection. mysqld by default closes idle connections after 8
hours.
> > -->
> > <parameter>
> > <name>url</name>
> > <value>jdbc:mysql://localhost:3306/test?autoReconnect=true</value>
> > </parameter>
> > </ResourceParams>
> > </Context>
> >
> > <!-- end stuff added to support dbcp -->
> >
> > (I've copied all my config stuff from here:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how
to.html)
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBCdriverclass'null'"
Posted by Jesse Keller <je...@aya.yale.edu>.
yeah, I've got
c:\tomcat\common\lib\mysql-connector-java-3.0.6-stable-bin.jar
I'll try the debug setting, and see what that tells me. The weird thing is
that I know the driver is there, and that it works, because I can use it
just fine when I don't try to do dbcp:
Class.forName("org.gjt.mm.mysql.Driver").newInstance();
conn = DriverManager.getConnection(DBUrl,"root","newpass");
stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery(stringSQL);
Question is, what's different about calling getConnection() this way instead
of the other way?
----- Original Message -----
From: "paul niemandt" <ma...@acesurfer.co.za>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, April 08, 2003 1:20 PM
Subject: Re: Basic JNDI setup problems - "Cannot load JDBCdriverclass'null'"
> OK: Sorry if I'm repeating a previous question or stating the obvious:
> but do you have a mysql-connector-java-xxx-bin.jar in
> c:\tomcat\common\lib ? This is the only real explanation I can think of
> now: The config looks correct, it's the same as mine, and mine does
> work!
>
> you can also set your debugging to full {change debug="0" to debug="100"
> wherever you can find it, and then scan the logs to see which libraries
> are loaded)
>
> On Tue, 2003-04-08 at 18:00, Jesse Keller wrote:
> > Thanks for the advice, Paul, but it looks like I'm not done yet -- I've
just
> > switched the server.xml file:
> >
> > <!-- Class name for mm.mysql JDBC driver -->
> > <parameter>
> > <name>driverClassName</name>
> > <value>com.mysql.jdbc.Driver</value>
> > </parameter>
> >
> > and restarted tomcat, but still no luck.
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "paul niemandt" <ma...@acesurfer.co.za>
> > To: "Tomcat Users List" <to...@jakarta.apache.org>
> > Sent: Tuesday, April 08, 2003 12:44 PM
> > Subject: Re: Basic JNDI setup problems - "Cannot load JDBC
> > driverclass'null'"
> >
> >
> > > Yeah: I would go with John on that: I don't use windows myself, so not
> > > too sure, but I would definitely install Tomcat under something like
> > > c:\tomcat rather than the full c:\program files\apache group\ kinda
> > > thingy.
> > >
> > > On the other hand, I had no success using org.gjt.mm.Driver, it was
only
> > > when I changed to com.mysql.jdbc.Driver that my servlet picked up the
> > > driver.
> > >
> > > {I used the mysql-connector-java-2.0.14 driver set}
> > >
> > > regards,
> > > Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBC
driverclass'null'"
Posted by paul niemandt <ma...@acesurfer.co.za>.
OK: Sorry if I'm repeating a previous question or stating the obvious:
but do you have a mysql-connector-java-xxx-bin.jar in
c:\tomcat\common\lib ? This is the only real explanation I can think of
now: The config looks correct, it's the same as mine, and mine does
work!
you can also set your debugging to full {change debug="0" to debug="100"
wherever you can find it, and then scan the logs to see which libraries
are loaded)
On Tue, 2003-04-08 at 18:00, Jesse Keller wrote:
> Thanks for the advice, Paul, but it looks like I'm not done yet -- I've just
> switched the server.xml file:
>
> <!-- Class name for mm.mysql JDBC driver -->
> <parameter>
> <name>driverClassName</name>
> <value>com.mysql.jdbc.Driver</value>
> </parameter>
>
> and restarted tomcat, but still no luck.
>
>
>
>
> ----- Original Message -----
> From: "paul niemandt" <ma...@acesurfer.co.za>
> To: "Tomcat Users List" <to...@jakarta.apache.org>
> Sent: Tuesday, April 08, 2003 12:44 PM
> Subject: Re: Basic JNDI setup problems - "Cannot load JDBC
> driverclass'null'"
>
>
> > Yeah: I would go with John on that: I don't use windows myself, so not
> > too sure, but I would definitely install Tomcat under something like
> > c:\tomcat rather than the full c:\program files\apache group\ kinda
> > thingy.
> >
> > On the other hand, I had no success using org.gjt.mm.Driver, it was only
> > when I changed to com.mysql.jdbc.Driver that my servlet picked up the
> > driver.
> >
> > {I used the mysql-connector-java-2.0.14 driver set}
> >
> > regards,
> > Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
paul niemandt <ma...@acesurfer.co.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBC driverclass'null'"
Posted by Jesse Keller <je...@aya.yale.edu>.
Thanks for the advice, Paul, but it looks like I'm not done yet -- I've just
switched the server.xml file:
<!-- Class name for mm.mysql JDBC driver -->
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
and restarted tomcat, but still no luck.
----- Original Message -----
From: "paul niemandt" <ma...@acesurfer.co.za>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, April 08, 2003 12:44 PM
Subject: Re: Basic JNDI setup problems - "Cannot load JDBC
driverclass'null'"
> Yeah: I would go with John on that: I don't use windows myself, so not
> too sure, but I would definitely install Tomcat under something like
> c:\tomcat rather than the full c:\program files\apache group\ kinda
> thingy.
>
> On the other hand, I had no success using org.gjt.mm.Driver, it was only
> when I changed to com.mysql.jdbc.Driver that my servlet picked up the
> driver.
>
> {I used the mysql-connector-java-2.0.14 driver set}
>
> regards,
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBC driver
class'null'"
Posted by paul niemandt <ma...@acesurfer.co.za>.
Yeah: I would go with John on that: I don't use windows myself, so not
too sure, but I would definitely install Tomcat under something like
c:\tomcat rather than the full c:\program files\apache group\ kinda
thingy.
On the other hand, I had no success using org.gjt.mm.Driver, it was only
when I changed to com.mysql.jdbc.Driver that my servlet picked up the
driver.
{I used the mysql-connector-java-2.0.14 driver set}
regards,
Paul
On Tue, 2003-04-08 at 17:22, John Turner wrote:
> No guarantee that this is the problem, but based on past posts to the list,
> pathnames with spaces should be avoided where/when possible.
>
> John
>
> On Tue, 8 Apr 2003 12:20:16 -0400, Jesse Keller <je...@aya.yale.edu>
> wrote:
>
> > Thanks, Paul. In my non-dbcp test servlet, I use
> >
> > Class.forName("org.gjt.mm.mysql.Driver").newInstance();
> >
> > with good results, so I don't think that's the problem. Is it possible
> > that
> > because it's a Windows system, the slashes in the path are confusing
> > Tomcat?
> >
> > C:\> echo %CATALINA_HOME%
> >
> > C:\Program Files\Apache Group\Tomcat 4.1
> >
> > C:\> cd %CATALINA_HOME%/common/lib
> >
> > C:\Program Files\Apache Group\Tomcat 4.1> -- windows doesn't see the
> > slashed path
> >
> > C:\>dir "C:\Program Files\Apache Group\Tomcat 4.1\common\lib\mysql*"
> >
> > Directory of C:\Program Files\Apache Group\Tomcat 4.1\common\lib
> >
> > 02/17/2003 12:17p 211,470
> > mysql-connector-java-3.0.6-stable-bin.jar
> >
> > ----- Original Message -----
> > From: "paul niemandt" <ma...@acesurfer.co.za>
> > To: <to...@jakarta.apache.org>
> > Sent: Tuesday, April 08, 2003 11:56 AM
> > Subject: Re: Basic JNDI setup problems - "Cannot load JDBC driver
> > class'null'"
> >
> >
> >> Either your mysql driver is not in $CATALINA_HOME/common/lib or you are
> >> using the wrong class name: try com.mysql.jdbc.Driver in stead of the
> >> mm.mysql thingy.
> >>
> >> [my guess, anyways]
> >>
> >> regards,
> >> Paul
> >>
> >> On Tue, 2003-04-08 at 16:42, Jesse Keller wrote:
> >> > I've seen lots of posts about this error message, but none of the
> >> posted
> > solutions seemed to apply. I'm running Tomcat 4.1 with MySQL connector/J
> > 3.0.6 on Win2000. I can connect to the database OK from a servlet without
> > dbcp, but when I try to use dbcp, it dies:
> >> >
> >> > Context ctx = new InitialContext();
> >> > DataSource ds =(DataSource)ctx.lookup("java:comp/env/jdbc/TestDB");
> >> > Connection conn = ds.getConnection();
> >> >
> >> > ctx.lookup() returns a non-null object. So far, so good. But
> > getConnection() throws java.sql.SQLException "Cannot load JDBC driver
> > class
> > 'null'"
> >> >
> >> > Thanks in advance for any help!
> >> >
> >> > Here's the relevant part of my server.xml:
> >> >
> >> > <!-- this stuff added to support dbcp -->
> >> >
> >> > <Context path="/DBTest2" docBase="DBTest2"
> >> > debug="5" reloadable="true" crossContext="true">
> >> >
> >> > <Logger className="org.apache.catalina.logger.FileLogger"
> >> > prefix="localhost_DBTest2_log." suffix=".txt"
> >> > timestamp="true"/>
> >> >
> >> > <Resource name="jdbc/TestDB"
> >> > auth="Container"
> >> > type="javax.sql.DataSource"/>
> >> >
> >> > <ResourceParams name="jdbc/TestDB">
> >> >
> >> > <parameter>
> >> > <name>factory</name>
> >> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
> >> > </parameter>
> >> >
> >> > <!-- Maximum number of dB connections in pool. Make sure you
> >> > configure your mysqld max_connections large enough to handle
> >> > all of your db connections. Set to 0 for no limit.
> >> > -->
> >> > <parameter>
> >> > <name>maxActive</name>
> >> > <value>5</value>
> >> > </parameter>
> >> >
> >> > <!-- Maximum number of idle dB connections to retain in pool.
> >> > Set to 0 for no limit.
> >> > -->
> >> > <parameter>
> >> > <name>maxIdle</name>
> >> > <value>3</value>
> >> > </parameter>
> >> >
> >> > <!-- Maximum time to wait for a dB connection to become available
> >> > in ms, in this example 10 seconds. An Exception is thrown if
> >> > this timeout is exceeded. Set to -1 to wait indefinitely.
> >> > -->
> >> > <parameter>
> >> > <name>maxWait</name>
> >> > <value>10000</value>
> >> > </parameter>
> >> >
> >> > <!-- MySQL dB username and password for dB connections -->
> >> > <parameter>
> >> > <name>username</name>
> >> > <value>root</value>
> >> > </parameter>
> >> > <parameter>
> >> > <name>password</name>
> >> > <value>newpass</value>
> >> > </parameter>
> >> >
> >> > <!-- Class name for mm.mysql JDBC driver -->
> >> > <parameter>
> >> > <name>driverClassName</name>
> >> > <value>org.gjt.mm.mysql.Driver</value>
> >> > </parameter>
> >> >
> >> > <!-- The JDBC connection url for connecting to your MySQL dB.
> >> > The autoReconnect=true argument to the url makes sure that
> >> the
> >> > mm.mysql JDBC Driver will automatically reconnect if mysqld
> > closed the
> >> > connection. mysqld by default closes idle connections after
> >> 8
> > hours.
> >> > -->
> >> > <parameter>
> >> > <name>url</name>
> >> >
> >> <value>jdbc:mysql://localhost:3306/test?autoReconnect=true</value>
> >> > </parameter>
> >> > </ResourceParams>
> >> > </Context>
> >> >
> >> > <!-- end stuff added to support dbcp -->
> >> >
> >> > (I've copied all my config stuff from here:
> > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-
> > how
> > to.html)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
--
paul niemandt <ma...@acesurfer.co.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBC driver class'null'"
Posted by Jesse Keller <je...@aya.yale.edu>.
Thanks for the suggestion, John.
Moved %CATALINA_HOME% to c:\tomcat, so there are no spaces in the paths
anymore. Restarted everything. Non-pooled access still works fine, pooled
access still throws "Cannot load JDBC driver class 'null' ".
Got another suggestion? There must be something simple and obvious I'm
overlooking -- how hard can this be?
----- Original Message -----
From: "John Turner" <to...@johnturner.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, April 08, 2003 12:22 PM
Subject: Re: Basic JNDI setup problems - "Cannot load JDBC driver
class'null'"
>
> No guarantee that this is the problem, but based on past posts to the
list,
> pathnames with spaces should be avoided where/when possible.
>
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Basic JNDI setup problems - "Cannot load JDBC driver class'null'"
Posted by John Turner <to...@johnturner.com>.
No guarantee that this is the problem, but based on past posts to the list,
pathnames with spaces should be avoided where/when possible.
John
On Tue, 8 Apr 2003 12:20:16 -0400, Jesse Keller <je...@aya.yale.edu>
wrote:
> Thanks, Paul. In my non-dbcp test servlet, I use
>
> Class.forName("org.gjt.mm.mysql.Driver").newInstance();
>
> with good results, so I don't think that's the problem. Is it possible
> that
> because it's a Windows system, the slashes in the path are confusing
> Tomcat?
>
> C:\> echo %CATALINA_HOME%
>
> C:\Program Files\Apache Group\Tomcat 4.1
>
> C:\> cd %CATALINA_HOME%/common/lib
>
> C:\Program Files\Apache Group\Tomcat 4.1> -- windows doesn't see the
> slashed path
>
> C:\>dir "C:\Program Files\Apache Group\Tomcat 4.1\common\lib\mysql*"
>
> Directory of C:\Program Files\Apache Group\Tomcat 4.1\common\lib
>
> 02/17/2003 12:17p 211,470
> mysql-connector-java-3.0.6-stable-bin.jar
>
> ----- Original Message -----
> From: "paul niemandt" <ma...@acesurfer.co.za>
> To: <to...@jakarta.apache.org>
> Sent: Tuesday, April 08, 2003 11:56 AM
> Subject: Re: Basic JNDI setup problems - "Cannot load JDBC driver
> class'null'"
>
>
>> Either your mysql driver is not in $CATALINA_HOME/common/lib or you are
>> using the wrong class name: try com.mysql.jdbc.Driver in stead of the
>> mm.mysql thingy.
>>
>> [my guess, anyways]
>>
>> regards,
>> Paul
>>
>> On Tue, 2003-04-08 at 16:42, Jesse Keller wrote:
>> > I've seen lots of posts about this error message, but none of the
>> posted
> solutions seemed to apply. I'm running Tomcat 4.1 with MySQL connector/J
> 3.0.6 on Win2000. I can connect to the database OK from a servlet without
> dbcp, but when I try to use dbcp, it dies:
>> >
>> > Context ctx = new InitialContext();
>> > DataSource ds =(DataSource)ctx.lookup("java:comp/env/jdbc/TestDB");
>> > Connection conn = ds.getConnection();
>> >
>> > ctx.lookup() returns a non-null object. So far, so good. But
> getConnection() throws java.sql.SQLException "Cannot load JDBC driver
> class
> 'null'"
>> >
>> > Thanks in advance for any help!
>> >
>> > Here's the relevant part of my server.xml:
>> >
>> > <!-- this stuff added to support dbcp -->
>> >
>> > <Context path="/DBTest2" docBase="DBTest2"
>> > debug="5" reloadable="true" crossContext="true">
>> >
>> > <Logger className="org.apache.catalina.logger.FileLogger"
>> > prefix="localhost_DBTest2_log." suffix=".txt"
>> > timestamp="true"/>
>> >
>> > <Resource name="jdbc/TestDB"
>> > auth="Container"
>> > type="javax.sql.DataSource"/>
>> >
>> > <ResourceParams name="jdbc/TestDB">
>> >
>> > <parameter>
>> > <name>factory</name>
>> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
>> > </parameter>
>> >
>> > <!-- Maximum number of dB connections in pool. Make sure you
>> > configure your mysqld max_connections large enough to handle
>> > all of your db connections. Set to 0 for no limit.
>> > -->
>> > <parameter>
>> > <name>maxActive</name>
>> > <value>5</value>
>> > </parameter>
>> >
>> > <!-- Maximum number of idle dB connections to retain in pool.
>> > Set to 0 for no limit.
>> > -->
>> > <parameter>
>> > <name>maxIdle</name>
>> > <value>3</value>
>> > </parameter>
>> >
>> > <!-- Maximum time to wait for a dB connection to become available
>> > in ms, in this example 10 seconds. An Exception is thrown if
>> > this timeout is exceeded. Set to -1 to wait indefinitely.
>> > -->
>> > <parameter>
>> > <name>maxWait</name>
>> > <value>10000</value>
>> > </parameter>
>> >
>> > <!-- MySQL dB username and password for dB connections -->
>> > <parameter>
>> > <name>username</name>
>> > <value>root</value>
>> > </parameter>
>> > <parameter>
>> > <name>password</name>
>> > <value>newpass</value>
>> > </parameter>
>> >
>> > <!-- Class name for mm.mysql JDBC driver -->
>> > <parameter>
>> > <name>driverClassName</name>
>> > <value>org.gjt.mm.mysql.Driver</value>
>> > </parameter>
>> >
>> > <!-- The JDBC connection url for connecting to your MySQL dB.
>> > The autoReconnect=true argument to the url makes sure that
>> the
>> > mm.mysql JDBC Driver will automatically reconnect if mysqld
> closed the
>> > connection. mysqld by default closes idle connections after
>> 8
> hours.
>> > -->
>> > <parameter>
>> > <name>url</name>
>> >
>> <value>jdbc:mysql://localhost:3306/test?autoReconnect=true</value>
>> > </parameter>
>> > </ResourceParams>
>> > </Context>
>> >
>> > <!-- end stuff added to support dbcp -->
>> >
>> > (I've copied all my config stuff from here:
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-
> how
> to.html)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org