KB-1072 Requests within the same session go to a different application server

Symptoms

When analyzing different requests within the same user session, through the use of web debugging proxies, the users observe that requests go to different application servers instead of using session stickiness. This can be observed in the JSESSION ID cookie at the end of the ID (for example, ABC122343.node1).

Cause

There is an improper configuration in standalone.xml or with session stickiness in the web server.

Action

  1. Verify session stickiness is enabled in the web server. If using Apache, verify worker.LoadBalancer.sticky_session=1 in httpd.conf, and if using IIS, verify worker.wlb.sticky_session=1 in workers.properties.
  2. If using JBoss, verify each node-id in standalone.xml matches the worker IDs in the web server's workers.properties.
  3. If using Tomcat, verify each DJVMRoute in setenv.bat|sh matches the worker IDs in the web server's worker.properties.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Related
Recommended