This bug occurs in upstream of WILDFLY and purpose of this bugzilla is possibility to track backport of functionality to the EAP 6.2.
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" />
*** Bug 971360 has been marked as a duplicate of this bug. ***
The attached customer case (#00889406) does not seem to be related to this issue. I am wondering, however, if they tried the hornetq journal based object store instead of the default one. It is a known feature that the default one is slow. But anyway, the case is already closed.
Verified for EAP 6.2.0.ER1.
Michael Musgrove <firstname.lastname@example.org> updated the status of jira JBTM-1879 to Closed