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

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

    XMLWordPrintable

Details

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

    Description

      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&gt;org.postgresql.Driver</driver-class&gt;
  <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" />

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFLY-1765 JDBC object store does not change LOG_STORE_TYPE attribute

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-1879 JdbcObjectStore is not closing connection

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-3104 datasource created with console cannot be enabled

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5020 Server fails to start with transactions configured to be run with JDBCObject store

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: