Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3488

Make orphan safety interval configurable without JVM restart

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 5.12.0.Final
    • None
    • JTA
    • None

    Description

      The attribute of orphan safety interval needs to be configurable without restaring JVM.

      It's one of the attributes which may speed up the finishing of the in-doubt transaction by recovery processing on suspended WildFly server (no new transactions are permitted to be started).

      This parameter to be configurable without JVM restart is needed for OpenShift scaledown processing and then especially for bootable jar which does not permit the WildFly :restart operation.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-3535 Make recovery config properties configurable without JVM restart

          • 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-14872 Upgrade Narayana to 5.12.0.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
          relates to

          Feature Request - Feature requests from customers and/or users WFLY-12610 Provide a proper :recover management operation for transactions

          • 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.
          • Pull Request Sent

          Requirement - Used for conducting internal reviews of our products and process with 3rd party auditors JBEAP-20714 Transaction recovery can not work in the context of Bootable Jar

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: