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

[GSS](7.2.z) Active session statistics incorrectly reported for invalidation caches

XMLWordPrintable

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

      Configure at least two clustered EAP instances to offload sessions to RHDG. (<invalidation-cache> with a <remote-store>).

      Configure the session cache for concurrent access (no <locking> or <transaction> tags).

      Deploy an application that uses sessions.

      Access the application on each node to create at least one session on each.

      Check the active sessions metric: /deployment=${deployment-name}/subsystem=undertow:read-attribute(name=active-sessions)

      Expected result: All instances report correct session counts.

      Actual result: One instance reports correct session counts, all others report 0.

      Show
      Configure at least two clustered EAP instances to offload sessions to RHDG. (<invalidation-cache> with a <remote-store>). Configure the session cache for concurrent access (no <locking> or <transaction> tags). Deploy an application that uses sessions. Access the application on each node to create at least one session on each. Check the active sessions metric: /deployment=${deployment-name}/subsystem=undertow:read-attribute(name=active-sessions) Expected result: All instances report correct session counts. Actual result: One instance reports correct session counts, all others report 0.

      The active session count returns the number of sessions in memory that are owned by the current member. For invalidation caches, sessions are always owned by the same member, thus all members except one will always return an active session count of 0.

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

              Created:
              Updated:
              Resolved: