4 Replies Latest reply on Apr 3, 2003 7:31 PM by David Jencks

    Please help *** mysql problem

    amalp Newbie

      here is my mysql-service.xml and it is under

      /server/default/deploy

      <?xml version="1.0" encoding="UTF-8" ?>
      - <!-- =====================================================================
      -->
      - <!--
      -->
      - <!-- JBoss Server Configuration
      -->
      - <!--
      -->
      - <!-- =====================================================================
      -->
      -
      - <!-- ====================================================================
      -->
      - <!-- New ConnectionManager setup for mysql using 2.0.11 driver
      -->
      - <!-- Build jmx-api (build/build.sh all) and view for config documentation
      -->
      - <!-- ====================================================================
      -->
      -
      - <!--
      Include a login module configuration named MySqlDbRealm.
      Update your login-conf.xml, here is an example for a
      ConfiguredIdentityLoginModule:

      <application-policy name = "MySqlDbRealm">

      <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
      <module-option name = "principal">yourprincipal</module-option>
      <module-option name = "userName">yourusername</module-option>
      <module-option name = "password">yourpassword</module-option>
      <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MySqlDS</module-option>
      </login-module>

      </application-policy>

      NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
      module-option name = "managedConnectionFactoryName"
      must match the object name of the ConnectionManager you are configuring here.


      -->
      - <!--
      uncomment out this line if you are using the MySqlDbRealm above
      MySqlDbRealm


      -->
      - <depends optional-attribute-name="ManagedConnectionFactoryName">
      - <!-- embedded mbean
      -->
      -
      MySqlDS
      -
      -
      <config-property name="ConnectionURL" type="java.lang.String">jdbc:mysql://localhost:3306/pac</config-property>
      <config-property name="DriverClass" type="java.lang.String">org.gjt.mm.mysql.Driver</config-property>
      - <!-- set these only if you want only default logins, not through JAAS
      -->
      <config-property name="UserName" type="java.lang.String">pacbean</config-property>
      <config-property name="Password" type="java.lang.String">pac100</config-property>


      - <!-- Below here are advanced properties
      -->
      - <!-- hack
      -->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper


      - <depends optional-attribute-name="ManagedConnectionPool">
      - <!-- embedded mbean
      -->
      -
      0
      50
      5000
      15
      - <!--
      criteria indicates if Subject (from security domain) or app supplied
      parameters (such as from getConnection(user, pw)) are used to distinguish
      connections in the pool. Choices are
      ByContainerAndApplication (use both),
      ByContainer (use Subject),
      ByApplication (use app supplied params only),
      ByNothing (all connections are equivalent, usually if adapter supports
      reauthentication)

      -->
      ByContainer


      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
      <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager
      java:/TransactionManager
      - <!-- make the rar deploy! hack till better deployment
      -->
      jboss.jca:service=RARDeployer





      Here is my AccountBean code where I get my conncection.

      at the top of the AccountBean I have

      private String dbName = "java:/MySqlDS";



      public void setEntityContext(EntityContext context)
      {

      this.context = context;
      try {
      makeConnection();

      } catch (Exception ex) {
      throw new EJBException("Unable to connect to database +
      ex.getMessage());
      }
      }

      and ...


      private void makeConnection() throws NamingException, SQLException
      {

      InitialContext ic = new InitialContext();
      DataSource ds = (DataSource) ic.lookup(dbName);
      con = ds.getConnection();


      }


      I am getting unable to connect to database "MySqlDS not bound" error.

      I been trying find the problem serverl days. I know I may did stupid mistake some where because I am new to EJB and Jboss.

      Please someone help me out....

      thanks
      Ap

        • 1. Re: Please help *** mysql problem
          David Jencks Master

          jboss version?????

          Study the server.log carefully, find the section where the mysql-service.xml is being deployed, and figure out why the errors there are occurring. If you can't figure out why, post the section of the log where this deployment is happening, complete.

          • 2. Re: Please help *** mysql problem
            amalp Newbie

            Hello,

            I have attached the server.log file. I could not figure out what is happaning. Please someone help me out to find out what is happaning.

            Thanks
            Ap

            • 3. Re: Please help *** mysql problem
              amalp Newbie

              Hello,

              I am have jboss-3.0.4-tomcat-4.1.12

              Here is the part of server.log where it try to load mysql-service.xml

              2003-04-02 08:14:37,326 WARN [org.jboss.system.ServiceController] jboss.jca:service=LocalTxDS,name=MySqlDS does not implement any Service methods
              2003-04-02 08:14:37,326 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Creating
              2003-04-02 08:14:37,326 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Created
              2003-04-02 08:14:37,326 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Starting
              2003-04-02 08:14:37,326 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Started
              2003-04-02 08:14:37,326 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/server/default/deploy/mysql-service.xml
              2003-04-02 08:14:37,326 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/server/default/deploy/properties-service.xml
              2003-04-02 08:14:37,346 INFO [org.jboss.deployment.MainDeployer] Package: file:/C:/jboss/server/default/lib/properties-plugin.jar is already deployed
              2003-04-02 08:14:37,346 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/server/default/deploy/properties-service.xml
              2003-04-02 08:14:37,346 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/server/default/deploy/scheduler-service.xml
              2003-04-02 08:14:37,366 INFO [org.jboss.deployment.MainDeployer] Package: file:/C:/jboss/server/default/lib/scheduler-plugin-example.jar is already deployed
              2003-04-02 08:14:37,376 INFO [org.jboss.deployment.MainDeployer] Package: file:/C:/jboss/server/default/lib/scheduler-plugin.jar is already deployed
              2003-04-02 08:14:37,376 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/server/default/deploy/scheduler-service.xml
              2003-04-02 08:14:37,376 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/server/default/deploy/tomcat41-service.xml
              2003-04-02 08:14:37,576 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/tomcat-4.1.x/common/lib/servlet.jar
              2003-04-02 08:14:37,636 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/tomcat-4.1.x/common/lib/servlet.jar
              2003-04-02 08:14:37,636 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/tomcat-4.1.x/common/lib/commons-logging-api.jar
              2003-04-02 08:14:37,667 WARN [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/jboss/tomcat-4.1.x/common/lib/commons-logging-api.jar references URL file:/C:/jboss/tomcat-4.1.x/common/lib/log4j.jar which could not be opened, entry ignored
              2003-04-02 08:14:37,667 WARN [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/jboss/tomcat-4.1.x/common/lib/commons-logging-api.jar references URL file:/C:/jboss/tomcat-4.1.x/common/lib/log4j-core.jar which could not be opened, entry ignored
              2003-04-02 08:14:37,667 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/tomcat-4.1.x/common/lib/commons-logging-api.jar
              2003-04-02 08:14:37,667 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss/tomcat-4.1.x/common/lib/jasper-compiler.jar
              2003-04-02 08:14:37,757 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss/tomcat-4.1.x/common/lib/jasper-compiler.jar

              thanks
              ap

              • 4. Re: Please help *** mysql problem
                David Jencks Master

                I think you have 2 or more copies of RARMetaData on your classpath. remove all but one. I don't remember the packaging in 3.0.4, maybe you copied a jar from deploy to lib??

                Anyway, the local wrapper .rar is not getting deployed due to an IllegalAccessError when a private method of RARMetaData is getting invoked by reflection from RARMetaData. The usual cause of these IllegalAccessError is duplicate classes.