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

Clustering AsynchronousService should stop asynchronously by default

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.CR1
    • 8.0.0.Beta1
    • Clustering
    • None

    Description

      By default, org.jboss.as.clustering.msc.AsynchronousService stops its service synchronously. This was done to workaround MSC ordering issues with stopping of dependent services. This no longer appears to be an issue.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2350 Services calling XAResourceRecoveryRegistry.removeXAResourceRecovery in stop must use MSC async API

          • 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

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: