tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38337] New: - GlobalNamingResource will not allow commercial DataSource drivers
Date Fri, 20 Jan 2006 20:33:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38337

           Summary: GlobalNamingResource will not allow commercial
                    DataSource drivers
           Product: Tomcat 5
           Version: Unknown
          Platform: All
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bloritsch@apache.org


We have the same datasource configurations for three webapps that we host on the
same server.  We want to merge those configurations into one place with
GlobalNamingResource.  The exact same configuration in the <Context> element
will not work with the <GlobalNamingResource> element.

Here is an example Resource config:

   <!-- NOTE: there are more configuration settings but this is the part that
        is important -->
   <Resource name="jdbc/cableds" auth="Container" 
              type="com.jnetdirect.jsql.JSQLPoolingDataSource"
              factory="org.apache.naming.factory.BeanFactory"
              serverName="ntncdsql3s" portNumber="1433"/>

When that configuration lives inside a <Context> element everything works as
expected.  When it lives inside a <GlobalNamingResource> Tomcat tries to use the
DBCP driver with the exception thrown:

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Canot create JDBC driver of
class '' for connect URL 'null'
 .... stack trace omitted ....

We do not want to use DBCP, we want to use the JNetDirect pooling drivers we
paid for.  Why is this happening?

We are using Tomcat 5.5.12 (sorry there was no entry for it here) on Windows. 
This seriously affects our deployment model as we will need to use the same
connections for server authentication in the very near future.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message