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

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

    XMLWordPrintable

Details

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

    Description

      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"/>

      Attachments

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

        Issue Links

          clones

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

          • 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-2486 JDBC object store closes connections after resultset/statements which is incorrect order

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBJCA-1286 Allow non-JTA datasources to run without a BootstrapContext

          • 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

          Release - A container task to coordinate the tasks for a given release. JBJCA-1291 IronJacamar 1.2.6.Final

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-5089 Upgrade Narayana to 5.2.2.Final

          • 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 related to

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

          • 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-5661 Enable CCM for jta=false

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: