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

[GSS](8.0.z) <max-active-sessions/> causes sessions to expire prematurely using the HotRod-based HttpSession manager

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 8.0.0.GA-CR1, 8.0.0.GA
    • 8.0.0.Beta
    • Clustering
    • None
    • False
    • None
    • False
    • Workaround Exists
    • Hide

      Remove <max-active-sessions/> from jboss-web.xml.
      This will have a negative impact on performance.

      Show
      Remove <max-active-sessions/> from jboss-web.xml. This will have a negative impact on performance.

      max-active-session enables the use of a near-cache within the HotRod client used by hotrod-session-management.
      Currently, session expiration is handled by applying a max-idle to a session's creation metadata. However, if near caching is enabled, subsequent reads of this entry do not touch the infinispan server, which means that session will always expire according to the session-timeout from the time they were created - regardless of how often the are accessed.

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

                Created:
                Updated:
                Resolved: