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

Interrupting session expiration task on shutdown can leave orphaned entries in cache

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 24.0.0.Final
    • 24.0.0.Beta1
    • Clustering
    • None

      Shutting down the server (or undeploying an application) currently performs an ExecutorService.shutdownNow(), which interrupts the session expiration task. If this task in the process of removing entries for an expired session, and the backing cache in non-transactional, this can result in stale cache entries which are no longer accessible.

      Instead we should use ExecutorService.shutdown(), and make the expiration task sensitive to shutdown state.

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

              Created:
              Updated:
              Resolved: