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

With transactional cache, expiration scheduling reads out of date maxInactiveInterval value changed on non-primary owner

XMLWordPrintable

      The scheduler uses a stale value in this case.

      Less of a real world scenario, more of a corner case uncovered by modifications to the expiration test case.

              pferraro@redhat.com Paul Ferraro
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: