In tomcat 5.5.9, defining the resources under the element seems to
have this kind of an issue. One way to resolve this is to define your
datasource (i.e, Resource) under Server/GlobalNamingResources element and
then define a ResourceLink in context.xml (in the same location as
server.xml). Hope this helps.
This worked for us.
Sastry Malladi,
Architect
SpikeSource
> I'm having difficulty defining a JNDI data source using C3P0 pooling in
> Tomcat 5.5.9. Here is the context descriptor for my app:
>
>
> verbosity="4" timestamp="true"/>
> reloadable="true" debug="1"/>
> name="jdbc/EmsDb"
> description="DB Connection"
> auth="Container"
> driverClass="net.sourceforge.jtds.jdbc.Driver"
> minPoolSize="5"
> maxPoolSize="10"
> acquireIncrement="1"
> user="sa"
> password=""
> factory="org.apache.naming.factory.BeanFactory"
> type="com.mchange.v2.c3p0.ComboPooledDataSource"
> jdbcUrl="jdbc:jtds:sqlserver://mars:1433/ems?autoReconnect=true"
> />
>
>
> Here is the resource-ref portion of my application descriptor:
>
>
> Database Connection
> jdbc/EmsDb
> javax.sql.DataSource
> Container
>
>
> And here is the error I get from Tomcat when deploying the application:
> 2005-09-27 00:55:33,559 [http-8080-Processor25] ERROR
> JDBCExceptionReporter - Cannot create JDBC driver of class '' for
> connect URL 'null'
>
> It almost seems as if the resource-ref is somehow overriding the
> Resource definition in the application context.
> Any suggestions?
>
> Thanks,
> Dave
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]