Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-19805

[GSS](7.2.z) Invalidation caches need to consider keys in the cache store when reassigning ownership

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.2.9.CR2, 7.2.9.GA
    • 7.2.8.GA
    • Clustering
    • None
    • +
    • Hide

      Configure EAP to offload sessions to RHDG. (<invalidation-cache> with a <remote-store>).

      Enable TRACE logging for "org.wildfly.clustering.web.infinispan"

      Deploy an application that uses sessions.

      Access the application to create a session.

      Restart EAP.

      Expected result: after the restart "Session X will expire in Y ms" for the session created above is logged.

      Actual result: "Session X will expire in Y ms" is not logged. Session never expires and remains in RHDG.

      Show
      Configure EAP to offload sessions to RHDG. (<invalidation-cache> with a <remote-store>). Enable TRACE logging for "org.wildfly.clustering.web.infinispan" Deploy an application that uses sessions. Access the application to create a session. Restart EAP. Expected result: after the restart "Session X will expire in Y ms" for the session created above is logged. Actual result: "Session X will expire in Y ms" is not logged. Session never expires and remains in RHDG.

    Description

      On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.

      This has the consequence of leaking memory for abandoned sessions.

      This also impacts replication caches that contain passivated entries.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: