1 Reply Latest reply on Aug 19, 2002 1:35 PM by brian

    MySQL Problems Version jboss-3.1.0alpha

    Anders Janmyr Newbie

      Hello,

      I have problems with MySql and version 3.1alpha. (I am using the alpha because of the ejb-relation bug found in version 3.0 and I can't find version 3.0.1 which is rumored to have the fix.)

      Has the configuration changed when using MySQL with JBoss and the latest version? If so where can I find information about it? I get the following error when using the configuration files from version 3.0.

      org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@34eb84 on mbean jboss.jca:service=LocalTxCM,name=MySqlDS; - nested throwable: (javax.management.AttributeNotFoundException: Writable attribute 'JaasSecurityManagerService' not found); - nested throwable: (org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@34eb84 on mbean jboss.jca:service=LocalTxCM,name=MySqlDS; - nested throwable: (javax.management.AttributeNotFoundException: Writable attribute 'JaasSecurityManagerService' not found))

        • 1. Re: MySQL Problems Version jboss-3.1.0alpha
          brian Newbie

          Hi,

          The configuration changes dramatically. It now requires you to have

          <application-policy name = "PostgresDbRealm">

          <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=TaiwuDS</module-option>
          </login-module>

          </application-policy>

          setup in the login-conf.xml. (In my case, it is PostgreSQL.) Please note that in the previous version (3.0.1), SecurityDomainJndiName was actually commented out. However, in this version, it is not. This was how I guessed to figure out how to config.

          <!--comment out this line if you want component managed security or want
          to use the default values in the ManagedConnectionFactoryProperties -->
          java:/jaas/PostgresDbRealm
          java:/TransactionManager

          You can find the sample configuration in the connector directory.

          I changed from 3.0.1 to 3.1.0aplha because I found two bugs. I fixed a simple one but another is way complicated to me. So, I gave up. Luckly I got 3.1.0alpha to work for me.

          One more thing. You may remove the hsqldb-service.xml if you don't need it. Two datasource may cause problems in this alpha version. Wierd.

          Brian