Uploaded image for project: ' WildFly Client Configuration'
  1. WildFly Client Configuration
  2. WFCC-22

Wildfly 14.0.1.FINAL not killing distributed sessions in a cluster even after idle time expiration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Blocker
    • None
    • None
    • None
    • Hide

      1. Intermittently one of the production nodes (we have a cluster of 3) becomes non-responsive - there are no error trace BUT server is up.
      2. When looked at the Wildfly console Runtime>Web(undertow) > Deployment > war ---> shows more than 90000 active sessions, even though there isnt that much traffic (this number keeps on growing).
      3. On doing rolling restart the sessions distribute over to other nodes but are never killed and this number keeps on growing until we completely stop all servers together.
      4. This is a concern since it impact our production environment.

      Show
      1. Intermittently one of the production nodes (we have a cluster of 3) becomes non-responsive - there are no error trace BUT server is up. 2. When looked at the Wildfly console Runtime>Web(undertow) > Deployment > war ---> shows more than 90000 active sessions, even though there isnt that much traffic (this number keeps on growing). 3. On doing rolling restart the sessions distribute over to other nodes but are never killed and this number keeps on growing until we completely stop all servers together. 4. This is a concern since it impact our production environment.

    Description

      Our platform upgraded to Wildfly 14.0.1.FINAL and we are experiencing below issue:-

      1. Intermittently one of the production nodes (we have a cluster of 3) becomes non-responsive - there are no error trace BUT server is up.
      2. When looked at the Wildfly console Runtime>Web(undertow) > Deployment > app.war ---> shows 90000+ active sessions.
      3. On doing rolling restart the sessions distribute over to other nodes but are never killed and this number keeps on growing until we completely stop all servers together.
      4. This is a concern since it impact our production environment.

      Please advise.

      Attachments

        Activity

          People

            ssur@redhat.com Sudeshna Sur
            arindram.mukherjee25@gmail.com Arin Mukherjee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: