5 Replies Latest reply on Mar 5, 2012 3:50 PM by sunil_patel

    JBoss 5.1.2 - Messaging datasource changing

    somostetoikilato

      Hi all,

       

      As sugerated in the documentation I changed the HSQLDB persistence service to ORACLE.

      I changed the values for all Datasource attibutes and I disabled the CreateTablesOnStartup

       

      But after restarting the JBoss I get an "ORA-00001: unique constraint violated" because it

      still wants to populate the JBM_DUAL table. Why? What else do I have to change?

       

      And I get the folowing errors too:

       

      DEPLOYMENTS MISSING DEPENDENCIES:

        Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:

          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")

          Dependency "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:

          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:

          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:

          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:

          Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")

        Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:

          Dependency "jboss.jgroups:service=ChannelFactory" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **")

       

      Any hint?

       

      SK

        • 1. Re: JBoss 5.1.2 - Messaging datasource changing
          wdfink

          I changed the values for all Datasource attibutes and I disabled the CreateTablesOnStartup

           

          But after restarting the JBoss I get an "ORA-00001: unique constraint violated" because it

          still wants to populate the JBM_DUAL table. Why? What else do I have to change?

           

          What you mean by change values for all datasources? What do you change?

          If you change from HSQLDB to Oracle you might replace the DefaultDS with an oracle and use the same name 'DefaultDS' or change the name in the messaging (and ejb-timer) configuration.

           

          Nevertheless you have to create the JMS tables for your oracleDS.

          • 2. Re: JBoss 5.1.2 - Messaging datasource changing
            somostetoikilato

            Hi Dieter,

            By "I changed the values for all Datasource attributes" I mean that the original DefaultDS datasource name was chaged according with the DS definition from deploy/oracle-ds.xml.

            More than that, I droped all JMS tables, I set the CreateTablesOnStartup to TRUE, I restarted the JBoss and as result I got eleven new tables, exactly those from deploy/messaging/oracle-persistence-service.xml.

            I stopped the JBoss, I set the CreateTablesOnStartup to FALSE, I restarted the JBoss and as result I get this exception:

            java.sql.PreparedStatement.executeUpdate
            INSERT INTO JBM_DUAL VALUES (1) parameters: {}
            throws exception: java.sql.SQLException: ORA-00001: unique constraint (SCHEMA.SYS_X022) violated
            java.sql.SQLException: ORA-00001: unique constraint (SCHEMA.SYS_X022) violated

            SK

            • 3. Re: JBoss 5.1.2 - Messaging datasource changing
              wdfink

              Mmmh, no idea.

              What if you do not change the CreateTablesOnStartup?

              If you see a stacktrace you might increase the logging level of the jboss package firering the SQL and see whether this will give  a hint.

              • 4. Re: JBoss 5.1.2 - Messaging datasource changing
                somostetoikilato

                Hi Dieter,

                 

                The logging is set to DEBUG level and this the only indice.

                 

                SK

                • 5. Re: JBoss 5.1.2 - Messaging datasource changing
                  sunil_patel

                  Do you have access to default installtion configuration and could you wipe everthing? Easy way out is to copy it to your configuration, drop all jboss created tables in your Oracle schema and change DefaultDs to point to Oracle.