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

Changing global transaction timeout requires reload to be considered for MDB

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 11.0.0.Alpha1
    • Transactions
    • None
    • Hide

      I'm trying to add testscase for this to WFLY by PR
      https://github.com/wildfly/wildfly/pull/9807
      see
      https://github.com/ochaloup/wildfly/commit/b846364566e9ab3e9c4bfa547ef7963b9c67feea

      For this could be test the setup task org.jboss.as.test.integration.ejb.transaction.mdb.timeout.TransactionDefaultTimeoutSetupTask needs to be updated to not contain server reload call ServerReload.executeReloadAndWaitForCompletion(managementClient.getControllerClient());
      could be run then
      ./integration-tests.sh clean install -Dts.noSmoke -Dts.basic -Dtest=MessageDrivenDefaultTimeoutTestCase

      Show
      I'm trying to add testscase for this to WFLY by PR https://github.com/wildfly/wildfly/pull/9807 see https://github.com/ochaloup/wildfly/commit/b846364566e9ab3e9c4bfa547ef7963b9c67feea For this could be test the setup task org.jboss.as.test.integration.ejb.transaction.mdb.timeout.TransactionDefaultTimeoutSetupTask needs to be updated to not contain server reload call ServerReload.executeReloadAndWaitForCompletion(managementClient.getControllerClient()); could be run then ./integration-tests.sh clean install -Dts.noSmoke -Dts.basic -Dtest=MessageDrivenDefaultTimeoutTestCase

    Description

      When default transaction timeout is redefined during the server lifetime

      /subsystem=transactions:write-attribute(name=default-timeout, value=60)
{"outcome" => "success"}

      such change is not propagated to WFTC and for example in case of MDB the default transaction timeout is being left as it was at time of container startup. The transaction timeout is considered after server is reloaded. But it's different behavior than it was and in general for transaction timeout redefinition should not be needed container reload.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9602 Changing global transaction timeout requires reload to be considered for MDB

          • 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.
          • Verified

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: