Link to home
Start Free TrialLog in
Avatar of geek4u
geek4u

asked on

JDBC Realm MYSQL connection

Hi, want to know where i am going wrong. Can someone look at my server.xml and tell me how i can establish the JDBC connection with the database. I am getting the following error all the time. I have also tried com.mysql.jdbc.Driver, it also gives me the same error. Is there anything that needs to be done with context etc.... Any help is appreciated.


Error in log file:
-----------------------------

JDBCRealm[Standalone]: Exception opening database connection
java.sql.SQLException: org.gjt.mm.mysql.Driver


My server.xml file:
---------------------------

<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
     parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
     which may contain one or more "Service" instances.  The Server
     listens for a shutdown command on the indicated port.

     Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" or "Loggers" at this level.
 -->

<Server port="8005" shutdown="SHUTDOWN" debug="0">


  <!-- Comment these entries out to disable JMX MBeans support -->
  <!-- You may also configure custom components (e.g. Valves/Realms) by
       including your own mbean-descriptor file(s), and setting the
       "descriptors" attribute to point to a ';' seperated list of paths
       (in the ClassLoader sense) of files to add to the default list.
       e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
  -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
            debug="0"/>
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
            debug="0"/>

  <!-- Global JNDI resources -->
  <GlobalNamingResources>

    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>

    <!-- 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">
    </Resource>
    <ResourceParams name="UserDatabase">
      <parameter>
        <name>factory</name>
        <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
      </parameter>
      <parameter>
        <name>pathname</name>
        <value>conf/tomcat-users.xml</value>
      </parameter>
    </ResourceParams>

  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" (and therefore the web applications visible
       within that Container).  Normally, that Container is an "Engine",
       but this is not required.

       Note:  A "Service" is not itself a "Container", so you may not
       define subcomponents such as "Valves" or "Loggers" at this level.
   -->

  <!-- Define the Tomcat Stand-Alone Service -->
  <Service name="Catalina">

    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned.  Each Connector passes requests on to the
         associated "Container" (normally an Engine) for processing.

         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
         You can also enable an SSL HTTP/1.1 Connector on port 8443 by
         following the instructions below and uncommenting the second Connector
         entry.  SSL support requires the following steps (see the SSL Config
         HOWTO in the Tomcat 5 documentation bundle for more detailed
         instructions):
         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
         * Execute:
             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
           with a password value of "changeit" for both the certificate and
           the keystore itself.

         By default, DNS lookups are enabled when a web application calls
         request.getRemoteHost().  This can have an adverse impact on
         performance, so you can disable it by setting the
         "enableLookups" attribute to "false".  When DNS lookups are disabled,
         request.getRemoteHost() will return the String version of the
         IP address of the remote client.
    -->

    <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
    <Connector port="8080"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" redirectPort="8443" acceptCount="100"
               debug="0" connectionTimeout="20000"
               disableUploadTimeout="true"
                                URIEncoding="UTF-8" />

    <!-- Note : To disable connection timeouts, set connectionTimeout value
     to 0 -->

        <!-- Note : To use gzip compression you could set the following properties :

                           compression="on"
                           compressionMinSize="2048"
                           noCompressionUserAgents="gozilla, traviata"
                           compressableMimeType="text/html,text/xml"
        -->

    <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" debug="0" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8009" minProcessors="5" maxProcessors="1200"
               enableLookups="true" redirectPort="8443"
               acceptCount="100" debug="0" connectionTimeout="0"
               useURIValidationHack="false"
               protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
-->
        <Connector port="8009"
                minProcessors="5"
                maxProcessors="600"
                enableLookups="false"
                redirectPort="8443"
                acceptCount="100"
                connectionTimeout="0"
                debug="0"
                protocol="AJP/1.3"
                URIEncoding="UTF-8"
        />

    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false"
               acceptCount="100" debug="0" connectionTimeout="20000"
               proxyPort="80" disableUploadTimeout="true" />
    -->

    <!-- 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). -->

    <!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
    <Engine name="Standalone" defaultHost="localhost" debug="0" jvmRoute="jvm1">        
        XXX
    -->

    <Engine jvmRoute="worker1" name="Standalone" defaultHost="localhost" debug="0">
         
    <!-- Define the top level container in our container hierarchy
    <Engine name="Catalina" defaultHost="localhost" debug="0">
        -->
   

      <!-- The request dumper valve dumps useful debugging information about
           the request headers and cookies that were received, and the response
           headers and cookies that were sent, for all requests received by
           this instance of Tomcat.  If you care only about requests to a
           particular virtual host, or a particular application, nest this
           element inside the corresponding <Host> or <Context> entry instead.

           For a similar mechanism that is portable to all Servlet 2.4
           containers, check out the "RequestDumperFilter" Filter in the
           example application (the source for this filter may be found in
           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

           Request dumping is disabled by default.  Uncomment the following
           element to enable it. -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- Global logger unless overridden at lower levels -->
      <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="catalina_log." suffix=".txt"
              timestamp="true"/>

      <!-- Because this Realm is here, an instance will be shared globally -->

      <!-- 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.  -->
      <!-- This has been commented and will be replaced by the JDBC MYSQL Realm -->
      <!--
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                 debug="0" resourceName="UserDatabase"/>
      -->

      <!-- Comment out the old realm but leave here for now in case we
           need to go back quickly -->
      <!--
      <Realm className="org.apache.catalina.realm.MemoryRealm" />
      -->

      <!-- Replace the above Realm with one of the following to get a Realm
           stored in a database and accessed via JDBC -->

     
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://172.31.254.103:3306/osfdb?user=xxxxxxxx&amp;password=xxxxxxx"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
   

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="sun.jdbc.odbc.JdbcOdbcDriver"
          connectionURL="jdbc:odbc:CATALINA"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

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

        <!-- Defines a cluster for this node,
             By defining this element, means that every manager will be changed.
             So when running a cluster, only make sure that you have webapps in there
             that need to be clustered and remove the other ones.
             A cluster has the following parameters:

             className = the fully qualified name of the cluster class

             name = a descriptive name for your cluster, can be anything

             debug = the debug level, higher means more output

             mcastAddr = the multicast address, has to be the same for all the nodes

             mcastPort = the multicast port, has to be the same for all the nodes
             
             mcastBindAddr = bind the multicast socket to a specific address
             
             mcastTTL = the multicast TTL if you want to limit your broadcast
             
             mcastSoTimeout = the multicast readtimeout

             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes

             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
                                in case of multiple ethernet cards.
                                auto means that address becomes
                                InetAddress.getLocalHost().getHostAddress()

             tcpListenPort = the tcp listen port

             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                  has a wakup bug in java.nio. Set to 0 for no timeout

             printToScreen = true means that managers will also print to std.out

             expireSessionsOnShutdown = true means that

             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                            false means to replicate the session after each request.
                            false means that replication would work for the following piece of code:
                            <%
                            HashMap map = (HashMap)session.getAttribute("map");
                            map.put("key","value");
                            %>
             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                               * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
                               * Synchronous means that the thread that executes the request, is also the
                               thread the replicates the data to the other nodes, and will not return until all
                               nodes have received the information.
                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                               so the request thread will queue the replication request into a "smart" queue,
                               and then return to the client.
                               The "smart" queue is a queue where when a session is added to the queue, and the same session
                               already exists in the queue from a previous request, that session will be replaced
                               in the queue instead of replicating two requests. This almost never happens, unless there is a
                               large network delay.
        -->            
        <!--
            When configuring for clustering, you also add in a valve to catch all the requests
            coming in, at the end of the request, the session may or may not be replicated.
            A session is replicated if and only if all the conditions are met:
            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
            2. a session exists (has been created)
            3. the request is not trapped by the "filter" attribute

            The filter attribute is to filter out requests that could not modify the session,
            hence we don't replicate the session after the end of this request.
            The filter is negative, ie, anything you put in the filter, you mean to filter out,
            ie, no replication will be done on requests that match one of the filters.
            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

            filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
            ending with .gif and .js are intercepted.
           
            The deployer element can be used to deploy apps cluster wide.
            Currently the deployment only deploys/undeploys to working members in the cluster
            so no WARs are copied upons startup of a broken node.
            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
            When a new war file is added the war gets deployed to the local instance,
            and then deployed to the other instances in the cluster.
            When a war file is deleted from the watchDir the war is undeployed locally
            and cluster wide
        -->
       
        <!--
        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true">

            <Membership
                className="org.apache.catalina.cluster.mcast.McastService"
                mcastAddr="228.0.0.4"
                mcastPort="45564"
                mcastFrequency="500"
                mcastDropTime="3000"/>

            <Receiver
                className="org.apache.catalina.cluster.tcp.ReplicationListener"
                tcpListenAddress="auto"
                tcpListenPort="4001"
                tcpSelectorTimeout="100"
                tcpThreadCount="6"/>

            <Sender
                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                replicationMode="pooled"/>

            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                   filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
                   
            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
        </Cluster>
        -->        



        <!-- Normally, users must authenticate themselves to each web app
             individually.  Uncomment the following entry if you would like
             a user to be authenticated the first time they encounter a
             resource protected by a security constraint, and then have that
             user identity maintained across *all* web applications contained
             in this virtual host. -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn"
                   debug="0"/>
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.AccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->

        <!-- Logger shared by all Contexts related to this virtual host.  By
             default (when using FileLogger), log files are created in the "logs"
             directory relative to $CATALINA_HOME.  If you wish, you can specify
             a different directory with the "directory" attribute.  Specify either a
             relative (to $CATALINA_HOME) or absolute path to the desired
             directory.-->
        <Logger className="org.apache.catalina.logger.FileLogger"
                 directory="logs"  prefix="localhost_log." suffix=".txt"
            timestamp="true"/>

        <!--Log4Web webapp -->
        <Context path="/Log4Web" docBase="Log4Web" debug="0" reloadable="true">
            <Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_log4web_log." suffix=".txt" timestamp="true" />
        </Context>


      </Host>

    </Engine>

  </Service>

</Server>

Avatar of CEHJ
CEHJ
Flag of United Kingdom of Great Britain and Northern Ireland image

>>
Error in log file:
-----------------------------

JDBCRealm[Standalone]: Exception opening database connection
java.sql.SQLException: org.gjt.mm.mysql.Driver
>>

Isn't there more than that?

Did you put the driver jar in %CATALINA_HOME%\common\lib?
Avatar of geek4u
geek4u

ASKER

ant.jar                      commons-dbcp-1.2.1.jar  jasper-compiler.jar  naming-common.jar   naming-resources.jar
ant-launcher.jar             commons-el.jar          jasper-runtime.jar   naming-factory.jar  servlet-api.jar
commons-collections-3.1.jar  commons-pool-1.2.jar    jsp-api.jar          naming-java.jar

are the jar files in my common/lib
Avatar of geek4u

ASKER

I guess i need to configure mysql in tomcat. Can you guide me how to do it? I have found resources on the net like

http://tomcat.apache.org/tomcat-4.1-doc/printer/jndi-datasource-examples-howto.html 

Is this the right procedure? Or is there any other resource on the net which is more clear. If you see in the above server.xml i guess context definition of the mysql driver is missing. Is that right??

*      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
*             driverName="org.gjt.mm.mysql.Driver"
*          connectionURL="jdbc:mysql://172.31.254.103:3306/osfdb?user=xxxxxxxx&amp;password=xxxxxxx"
*              userTable="users" userNameCol="user_name" userCredCol="user_pass"
*          userRoleTable="user_roles" roleNameCol="role_name" />

Try this instead,

      <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://172.31.254.103:3306/osfdb"
           connectionName="<USER NAME>" connectionPassword="<PASSWORD>"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />


Also my guess on the other side is, make sure you have the MYSQL jars placed on the classpath of the server.  Sometimes, it throws back a different exception when the DRIVER is not found in the classpath.  

Search for mysql-connector-java-3.0.16-ga-bin.jar (or whatever jar that is given by MYSQL) in your classpath.


Good luck!
It took me to type more than 10 mins, by the time CEHJ got into the same point of what I am thinking :)
Avatar of geek4u

ASKER

How to find whether the jar file is in my class path? and also is there no need to configure the mysql by declaring the resource in server.xml as shown in the above link?
ASKER CERTIFIED SOLUTION
Avatar of mmuruganandam
mmuruganandam
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The link that you have posted is talking about Datasource.  I am not sure of what is your requirement.  By what you are doing now, is to connect to a table for user roles (roles and authorization)...    From TOMCAT 4, you can do that using the datasources too...
Read here for more information on how to setup the JDBC Realm and also using the DataSourceRealm.

http://tomcat.apache.org/tomcat-4.1-doc/realm-howto.html#JDBCRealm
Avatar of geek4u

ASKER

I want to use JDBC realm only i.e, i am trying to connect to the mysql database using a driver. But everytime i try to connect it gives me a driver exception. I guess you are right. The driver is not in the class path or driver is not at all there!! Can you tell me how to find out whether the driver is there or not or what is the default driver in tomcat? Any help will be appreciated.

Thanks,
These drivers doesn't come with TOMCAT.

Download this...
http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-3.1.12.zip/from/http://mirror.services.wisc.edu/mysql/

and

Extract the file mysql-connector-java-3.1.12-bin.jar and put into $CATALINA_HOME/server/lib
>>Can you tell me how to find out whether the driver is there or not or what is the default driver in tomcat?

You need to put the driver jar where i said. Often the driver jar is mysql.jar. If there's any doubt, try downloading the ltest and put it in there
To explain you little more,

You can put your jars only in $CATALINA_HOME/server/lib if you like to use these jars only for your server purpose.

You can put it into %CATALINA_HOME%\common\lib if you like to use the JAR's for all the deployed application which needs to use your MySQL as database.
Avatar of geek4u

ASKER

So from the common/lib folder details i have given, it is evident that mysql driver is not there. Right?? I have extracted file from zip but i need to make them .jar right?? and put it in common/lib let me know.
You need to unpack the download and put the jars in there
> I have extracted file from zip but i need to make them .jar right??

No, it already contains a jar
I told you to put the jar in common/lib in your previous question, did that not work for you?
You really didn't need to ask a new question to get the answer again.
Avatar of geek4u

ASKER

I just want to recap on the whole thing cos i am just waiting for my supervisor to restart the server and i dont have access to it and he is away.  Just to make sure before you guys go away-

1) I have changed the Realm in the server.xml file to

<Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="com.mysql.jdbc.Driver"
          connectionURL="jdbc:mysql://172.31.254.103:3306/osfdb?user=xxxxx&amp;password=xxxxxx"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />

2) I have installed the mysql driver by placing the jar file of the driver into tomcat/common/lib

3) I had already created tables in the mysql database for users, user_roles and roles

Is there anything else that is required to be done? I dont need to declare the context in server.xml for JDBC realm. Right?? I dont need to change anything in web.xml. right??

Please let me know. I am waiting to c the changes i did so far.

Thanks
I don't think so...

But try with

 <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://172.31.254.103:3306/osfdb"
           connectionName="<USER NAME>" connectionPassword="<PASSWORD>"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />


Instead of having the user and password in the connection URL.
> i am just waiting for my supervisor to restart the server and i dont have access to it and he is away.

may be worth you setting up a local server that you can use for your own testing :)
:)

Regards,
Muruga
----------------------------------------------------------------------------
Tryout personalized emailing services at http://www.mailaide.com
geek4u, can you tell me why you accepted that answer? I had already told you what your problem was and how to solve it
Avatar of geek4u

ASKER

I am very thankful to CEHJ as well. I felt that Muruga spent a great deal of time in helping me fix the problem. Pl CEHJ no hard feelings. I thank u guys from the bottom of my heart.
Then it should have been a points split. The accepted answer (by m's admission) simply reiterates my earlier comments
Avatar of geek4u

ASKER

Sorry for that. Cheers guys.
CEHJ, I agree to your point of SPLIT (which would have been really good).  But DON'T say simply reiterates.  That hurts!  I have already posted that, by the time, i submitted my answer, you have posted...

I don't need this POINT...

But LET US NOT hurt each other!
I'm only going on what you said m - i'm not accusing you of anything ;-)

>>It took me to type more than 10 mins, by the time CEHJ got into the same point of what I am thinking :)
No problem dude!  If there is a chance to post this for a SPLIT or even you deserve this point completely.  Even though, I thought of this answer, you have posted first.  But I didn't see your answer, until I post my answer :)

Anyway, look at the possibilities...