Tomcat 6.0.14 and DataAccessException

Help
2011-02-04
2012-12-06
  • Sergio Szychowski

    Hi,
    can't start plandora, cause this exception

    com.pandora.exception.DataAccessException: com.pandora.exception.DataAccessException: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null'
            at com.pandora.dao.ReportDAO.getReportListToPerfom(ReportDAO.java:243)
            at com.pandora.bus.ReportBUS.performKPI(ReportBUS.java:158)
            at com.pandora.delegate.ReportDelegate.performKPI(ReportDelegate.java:79)
            at com.pandora.bus.GeneralTimer.onTimer(GeneralTimer.java:96)
            at com.pandora.bus.GeneralTimer.run(GeneralTimer.java:76)
            at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.NullPointerException
            at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(JdbcOdbcDriver.java:507)
            at sun.jdbc.odbc.JdbcOdbcDriver.knownURL(JdbcOdbcDriver.java:476)
            at sun.jdbc.odbc.JdbcOdbcDriver.acceptsURL(JdbcOdbcDriver.java:307)
            at java.sql.DriverManager.getDriver(DriverManager.java:253)
            at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
            at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
            at com.pandora.dao.DataAccess.getConnection(DataAccess.java:65)
            at com.pandora.dao.DataAccess.getConnection(DataAccess.java:44)
            at com.pandora.dao.ReportDAO.getReportListToPerfom(ReportDAO.java:240)
            … 5 more

    this is the server.xml contents

    <!- Note:  A "Server" is not itself a "Container", so you may not
         define subcomponents such as "Valves" at this level.
         Documentation at /docs/config/server.html
    ->
    <Server port="8005" shutdown="SHUTDOWN">

      <!-APR library loader. Documentation at /docs/apr.html ->
      <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
      <!-Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html ->
      <Listener className="org.apache.catalina.core.JasperListener" />
      <!- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html ->
      <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
      <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

      <!- Global JNDI resources
           Documentation at /docs/jndi-resources-howto.html
      ->
      <GlobalNamingResources>
        <!- Editable user database that can also be used by
             UserDatabaseRealm to authenticate users
        ->
        <Resource name="UserDatabase" auth="Container"
                  type="org.apache.catalina.UserDatabase"
                  description="User database that can be updated and saved"
                  factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
                  pathname="conf/tomcat-users.xml" />
      </GlobalNamingResources>

      <!- A "Service" is a collection of one or more "Connectors" that share
           a single "Container" Note:  A "Service" is not itself a "Container",
           so you may not define subcomponents such as "Valves" at this level.
           Documentation at /docs/config/service.html
       ->
      <Service name="Catalina">
     
        <!-The connectors can use a shared executor, you can define one or more named thread pools->
        <!-
        <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
            maxThreads="150" minSpareThreads="4"/>
        ->
       
       
        <!- A "Connector" represents an endpoint by which requests are received
             and responses are returned. Documentation at :
             Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
             Java AJP  Connector: /docs/config/ajp.html
             APR (HTTP/AJP) Connector: /docs/apr.html
             Define a non-SSL HTTP/1.1 Connector on port 8080
        ->
        <Connector port="8080" protocol="HTTP/1.1"
                   connectionTimeout="20000"
                   redirectPort="8443" />
        <!- A "Connector" using the shared thread pool->
        <!-
        <Connector executor="tomcatThreadPool"
                   port="8080" protocol="HTTP/1.1"
                   connectionTimeout="20000"
                   redirectPort="8443" />
        ->          
        <!- Define a SSL HTTP/1.1 Connector on port 8443
             This connector uses the JSSE configuration, when using APR, the
             connector should be using the OpenSSL style configuration
             described in the APR documentation ->
        <!-
        <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                   maxThreads="150" scheme="https" secure="true"
                   clientAuth="false" sslProtocol="TLS" />
        ->

        <!- Define an AJP 1.3 Connector on port 8009 ->
        <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />

        <!- An Engine represents the entry point (within Catalina) that processes
             every request.  The Engine implementation for Tomcat stand alone
             analyzes the HTTP headers included with the request, and passes them
             on to the appropriate Host (virtual host).
             Documentation at /docs/config/engine.html ->

        <!- You should set jvmRoute to support load-balancing via AJP ie :
        <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">        
        ->
        <Engine name="Catalina" defaultHost="localhost">

          <!-For clustering, please take a look at documentation at:
              /docs/cluster-howto.html  (simple how to)
              /docs/config/cluster.html (reference documentation) ->
          <!-
          <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
          ->       

          <!- The request dumper valve dumps useful debugging information about
               the request and response data received and sent by Tomcat.
               Documentation at: /docs/config/valve.html ->
          <!-
          <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
          ->

          <!- This Realm uses the UserDatabase configured in the global JNDI
               resources under the key "UserDatabase".  Any edits
               that are performed against this UserDatabase are immediately
               available for use by the Realm.  ->
          <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                 resourceName="UserDatabase"/>

          <!- Define the default virtual host
               Note: XML Schema validation will not work with Xerces 2.2.
           ->
          <Host name="localhost"  appBase="webapps"
                unpackWARs="true" autoDeploy="true"
                xmlValidation="false" xmlNamespaceAware="false">

            <!- SingleSignOn valve, share authentication between web applications
                 Documentation at: /docs/config/valve.html ->
            <!-
            <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
            ->

            <!- Access log processes all example.
                 Documentation at: /docs/config/valve.html ->
            <!-
            <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" 
                   prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
            ->

                    <DefaultContext>
                            <Resource name="jdbc/plandora" description="PLANdora DB Connection" auth="Container" type="javax.sql.DataSource" scope="Shareable"/>
                                    <ResourceParams name="jdbc/plandora">
                                    <parameter><name>factory</name><value>org.apache.commons.dbcp.BasicDataSourceFactory</value></parameter>
                                    <parameter><name>driverClassName</name><value>com.mysql.jdbc.Driver</value></parameter>
                                    <parameter><name>url</name><value>jdbc:mysql://localhost:3306/db_plandora</value></parameter>
                                    <parameter><name>username</name><value>usr_pandora</value></parameter>
                                    <parameter><name>password</name><value>plandora</value></parameter>
                                    <parameter><name>maxActive</name><value>50</value></parameter>
                                    <parameter><name>maxIdle</name><value>20</value></parameter>
                                    <parameter><name>maxWait</name><value>10000</value></parameter>
                            </ResourceParams>
                    </DefaultContext>

          </Host>
        </Engine>
      </Service>
    </Server>

     
  • Alberto Pereto

    Alberto Pereto - 2011-02-04

    Hi Sergio, how are you.

    I can see in the title of your post that you are using Tomcat 6.0.14.
    In this case, you should change the context.xml file, instead the server.xml.

    Check the Installation Process at http://plandora.sourceforge.net/project.htm at "third step". Note that there is a difference between the setup of "Tomcat 5.3.x or higher" and older versions on Tomcat.

    Dont forget to restore the previous server.xml. ;-)

    Try this and give me your feedback.
    Thank you very much.

     
  • Sergio Szychowski

    Thanks Alberto,

    i can fix, but the context.xml was added in "pandora/META-INF/ " folder,  note that  if adding inside  "tomcat/conf/context.xml"  not work.

    and the contents of  "pandora/META-INF/context.xml"

    <Context >
       <Resource name="jdbc/plandora" description="PLANdora DB Connection" auth="Container"
                   type="javax.sql.DataSource"
                   driverClassName="com.mysql.jdbc.Driver"
                   maxActive="100" maxIdle="30" maxWait="1000"
                   username="sergio_plandora"
                   password="plandora"
                   url="jdbc:mysql://localhost:3306/sergio_plandora"/>
    </Context>

     
  • Alberto Pereto

    Alberto Pereto - 2011-02-07

    Hi Sergio, I'm really surprised with your comment.

    Here, in my environment, and at the company that I work, I put the context.xml file into /tomcat/conf folder, replacing the current file and everything works appropriately.

    Anyway, thank you for your feedback. I will change the Installation Process to include your issue.

    Thank you.

    Alberto Pereto

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks