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

Session affinity information is attached to the session ID but never used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 8.1.0.GA
    • 8.0.0.GA
    • Cloud Galleon Pack
    • None

      Previously WildFly only supported the ability to encode session affinity information into the JSESSIONID cookie, which is already used to uniquely identify a session. While this works well with the httpd family of load balancer modules (e.g. mod_cluster, mod_proxy_balancer, mod_jk) for which this mechanism was designed, however, the current set of load balancers used in the cloud rely on a separate cookie for implementing sticky sessions (e.g. HAProxy, IIS, etc.), and thus we lack the ability to allow WildFly to guide requests for a given session to the server that can most efficiently handle it.

      To resolve this, we need to configure the Undertow subsystem to use a separate cookie to send affinity information.

              rhn-engineering-rhusar Radoslav Husar
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: