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

Web sessions passivated on shutdown even if the cache store purges on startup

    XMLWordPrintable

Details

    • Hide

      Deploy a web application configured as <distributable/>.
      Create sessions.
      Undeploy the application and/or shut down EAP.

      Observe the size of the file store, and the logs:
      14:50:27,830 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool – 86) ISPN000030: Passivated 33 entries in 6 milliseconds

      Expected behavior: "empty" file store (with only metadata) and log reporting 0 entries passivated.

      Show
      Deploy a web application configured as <distributable/>. Create sessions. Undeploy the application and/or shut down EAP. Observe the size of the file store, and the logs: 14:50:27,830 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool – 86) ISPN000030: Passivated 33 entries in 6 milliseconds Expected behavior: "empty" file store (with only metadata) and log reporting 0 entries passivated.
    • Workaround Exists
    • Hide

      Remove <file-store> from the web session cache.
      (Only if no application using the cache has max-active-sessions configured)

      Show
      Remove <file-store> from the web session cache. (Only if no application using the cache has max-active-sessions configured)

    Description

      With the default HA configuration, when a <distributable/> web application is stopped its sessions are persisted to disk. No max-active-sessions configuration used.

      This is a performance issue. It does not affect functionality, because the store is purged on startup.

      It affects all EAP 7 versions tested. It does not occur in EAP 6.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18445 [GSS](7.3.z) Web sessions passivated on shutdown

          • 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.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: