7 Replies Latest reply on Sep 19, 2014 4:53 AM by Venkata Ramana Murthy Kanukollu

    datasource binding for CMP

    Arun Varadharajan Newbie

      I'm using jboss7.1.1 final.

       

      I have defined by datasoruce in standalone-fill-ha.xml as below:

       

      <subsystem xmlns="urn:jboss:domain:datasources:1.0">
                  <datasources>
                      <datasource jta="false" jndi-name="java:/GemDataSource" pool-name="GemDataSource" enabled="true" use-ccm="false">
                          <connection-url>jdbc:hsqldb:mem:.</connection-url>
                          <driver-class>org.hsqldb.jdbcDriver</driver-class>
                          <connection-property name="sql.syntax_mys">
                              true
                          </connection-property>
                          <driver>hsql</driver>
                          <pool>
                              <max-pool-size>20</max-pool-size>
                              <prefill>true</prefill>
                          </pool>
                          <security>
                              <user-name>sa</user-name>
                              <security-domain>HsqlDbRealm</security-domain>
                          </security>
                          <validation>
                              <validate-on-match>false</validate-on-match>
                              <background-validation>false</background-validation>
                          </validation>
                          <statement>
                              <share-prepared-statements>false</share-prepared-statements>
                          </statement>
                      </datasource>
                      <drivers>
                          <driver name="hsql" module="org.hsqldb">
                              <driver-class>org.hsqldb.jdbcDriver</driver-class>
                          </driver>
                      </drivers>
                  </datasources>
              </subsystem>
      

       

      On the console, I'm getting missing dependices as follows

       

       

                service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.ALM.jdbc.store-manager.INIT (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.relations-barr
            service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.ALM.jdbc.store-manager.RELATIONS (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.start-barrier] 
            service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.ALM.jdbc.store-manager.START (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.fk-barrier] 
            service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.AlmTL1RootObject.jdbc.store-manager.INIT (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.relations-barrier] 
            service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.AlmTL1RootObject.jdbc.store-manager.RELATIONS (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.start-barrier] 
            service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".component.AlmTL1RootObject.jdbc.store-manager.START (missing) dependents: [service jboss.deployment.subunit."zicEAR.ear"."ejb-jar-tl1-tl1layer.jar".jdbc.store-manager.fk-barrier]