Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5020

Server fails to start with transactions configured to be run with JDBCObject store

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 10.0.0.CR4
    • None
    • Transactions
    • None

      When you configure transactions subsystem for running with JDBCObject store, the app server fails to start because of a error below.

      Error message:

      ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]): org.jboss.msc.service.CircularDependencyException: Container jboss-as has a circular dependency: [service jboss.txn.ArjunaObjectStoreEnvironment, service jboss.txn.ArjunaRecoveryManager, service jboss.connector.transactionintegration, service jboss.rarepository, service jboss.data-source.java:jboss/datasources/jdbc-store, service jboss.data-source.reference-factory.JDBCPool, service jboss.naming.context.java.jboss.datasources.jdbc-store]
      

      Datasource configuration is:

      <datasource jta="false" jndi-name="java:jboss/datasources/jdbc-store" pool-name="JDBCPool" enabled="true" use-java-context="true">
      <connection-url>jdbc:sqlserver://mssql2014server:1433;DatabaseName=database1</connection-url>
      <driver>sqljdbc4.jar</driver>
      <security>
        <user-name>username1</user-name>
        <password>password1</password>
      </security>
      </datasource>
      

      and the transaction config looks like this

      <jdbc-store datasource-jndi-name="java:jboss/datasources/jdbc-store"/>
      

        1. standalone.xml
          21 kB
        2. standalone_module.xml
          21 kB
        3. server.log
          24 kB
        4. server_module.log
          22 kB

              smaestri@redhat.com Stefano Maestri
              hhovsepy@redhat.com Hayk Hovsepyan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: