[
https://issues.jboss.org/browse/WFLY-1460?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1460:
-----------------------------------------------
Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug
971358|https://bugzilla.redhat.com/show_bug.cgi?id=971358]
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">
<connection-url>jdbc:postgresql://postgresserver.com:5432/user1</connection-url>
<driver-class>org.postgresql.Driver</driver-class>
<driver>postgresql-9.2-1002.jdbc4.jar</driver>
<security>
<user-name>user1</user-name>
<password>user1</password>
</security>
</datasource>
and the transaction config looks like this
<jdbc-store datasource-jndi-name="java:jboss/datasources/JDBCObjectDS" />
WildFly server fails to start with transactions configured to be run
with JDBCObject store
------------------------------------------------------------------------------------------
Key: WFLY-1460
URL:
https://issues.jboss.org/browse/WFLY-1460
Project: WildFly
Issue Type: Bug
Components: Transactions
Affects Versions: 8.0.0.Alpha1
Reporter: Ondřej Chaloupka
Assignee: Stefano Maestri
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:
{code}
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]
{code}
My assumption came from the configuration similar to this:
{code}
<datasource jta="false"
jndi-name="java:jboss/datasources/JDBCObjectDS"
pool-name="JDBCObjectDS" enabled="true" use-ccm="false">
<connection-url>jdbc:postgresql://postgresserver.com:5432/user1</connection-url>
<driver-class>org.postgresql.Driver</driver-class>
<driver>postgresql-9.2-1002.jdbc4.jar</driver>
<security>
<user-name>user1</user-name>
<password>user1</password>
</security>
</datasource>
{code}
and the transaction config looks like this
{code}
<jdbc-store datasource-jndi-name="java:jboss/datasources/JDBCObjectDS"
/>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira