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

WildFly server fails to start with transactions configured to be run with JDBCObject store


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 10.0.0.Final
    • 8.0.0.Alpha1
    • Transactions
    • None

      In case that you configure transactions subsystem for running with JDBCObject store the app server fails to start because of (it seems so) a circular dependency.

      You can expect the exception like:

      ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 52) JBAS014612: 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.cached-connection-manager, service jboss.data-source.java:jboss/datasources/JDBCObjectDS] 

      My assumption came from the configuration similar to this:

      <datasource jta="false" jndi-name="java:jboss/datasources/JDBCObjectDS" pool-name="JDBCObjectDS" enabled="true" use-ccm="false"> 

      and the transaction config looks like this

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

            smaestri@redhat.com Stefano Maestri
            ochaloup@redhat.com Ondrej Chaloupka (Inactive)
            1 Vote for this issue
            6 Start watching this issue