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

Failure to commit state shouldn't trigger response failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.CR5
    • 10.0.0.CR4
    • Clustering
    • None

    Description

      We should log a warning instead, ideally commit data to the local node (e.g. AS5/AS7 behavior).

      In sync case its too late to propagate to undertow because the response was already commited.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1957 Failure to commit state shouldn't trigger response failure

          • 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
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: