https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-serveren-USTelligent Community 12https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-serverWed, 10 Oct 2018 05:17:46 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33750534-fc61-48a1-b957-b400ea24b226Jordan Horwathttps://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server#commentsCurrent Revision posted to Appian Knowledge Base by Jordan Horwat on 10/10/2018 5:17:46 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>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).</p> <h2 id="cause">Cause</h2> <p>There is an improper configuration in <strong>standalone.xml</strong> or with session stickiness in the web server.</p> <h2 id="action">Action</h2> <ol> <li>Verify session stickiness is enabled in the web server. If using Apache, verify <code>worker.LoadBalancer.sticky_session=1</code> in <strong>httpd.conf</strong>, and if using IIS, verify <code>worker.wlb.sticky_session=1</code>&nbsp;in <strong>workers.properties</strong>.</li> <li>If using JBoss, verify each <code>node-id</code> in <strong>standalone.xml</strong> matches the worker IDs in the web server&#39;s <strong>workers.properties</strong>.</li> <li>If using Tomcat, verify each DJVMRoute in&nbsp;<strong>setenv.bat|sh</strong>&nbsp;matches the worker IDs in the web server&#39;s <strong>worker.properties</strong>.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;October 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web server, application server, infrastructure</div> https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server/revision/4Wed, 10 Oct 2018 05:14:59 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33750534-fc61-48a1-b957-b400ea24b226Jordan Horwathttps://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server#commentsRevision 4 posted to Appian Knowledge Base by Jordan Horwat on 10/10/2018 5:14:59 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>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).</p> <h2 id="cause">Cause</h2> <p>There is an improper configuration in <strong>standalone.xml</strong> or with session stickiness in the web server.</p> <h2 id="action">Action</h2> <ol> <li>Verify session stickiness is enabled in the web server. If using Apache, verify <code>worker.LoadBalancer.sticky_session=1</code> in <strong>httpd.conf</strong>, and if using IIS, verify <code>worker.wlb.sticky_session=1</code>&nbsp;in <strong>workers.properties</strong>.</li> <li>If using JBoss, verify each <code>node-id</code> in <strong>standalone.xml</strong> matches the worker IDs in the web server&#39;s <strong>workers.properties</strong>.</li> <li>If using Tomcat, verify each DJVMRoute in&nbsp;<strong>setenv.bat|sh</strong>&nbsp;matches the worker IDs in the web server&#39;s worker.properties.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;October 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web server, application server, infrastructure</div> https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server/revision/3Wed, 10 Oct 2018 04:57:02 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33750534-fc61-48a1-b957-b400ea24b226Jordan Horwathttps://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server#commentsRevision 3 posted to Appian Knowledge Base by Jordan Horwat on 10/10/2018 4:57:02 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>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).</p> <h2 id="cause">Cause</h2> <p>There is an improper configuration in <strong>standalone.xml</strong> or with session stickiness in the web server.</p> <h2 id="action">Action</h2> <ol> <li>Verify session stickiness is enabled in the web server. If using Apache, verify <code>worker.LoadBalancer.sticky_session=1</code> in <strong>httpd.conf</strong>, and if using IIS, verify <code>worker.wlb.sticky_session=1</code>&nbsp;in <strong>workers.properties</strong>.</li> <li>If using JBoss, verify each <code>node-id</code> in <strong>standalone.xml</strong> matches the worker IDs in the web server&#39;s <strong>workers.properties</strong>.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web server, application server, infrastructure</div> https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server/revision/2Mon, 30 Jul 2018 03:56:08 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33750534-fc61-48a1-b957-b400ea24b226Parmida Borhanihttps://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server#commentsRevision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:56:08 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>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).</p> <h2 id="cause">Cause</h2> <p>There is an improper configuration in <strong>standalone.xml</strong> or with session stickiness in the web server.</p> <h2 id="action">Action</h2> <ol> <li>Verify session stickiness is enabled in the web server. If using Apache, verify <code>worker.LoadBalancer.sticky_session=1</code> in <strong>httpd.conf</strong>, and if using IIS, verify <code>worker.wlb.sticky_session=1</code>in <strong>workers.properties</strong>.</li> <li>If using JBoss, verify each <code>node-id</code> in <strong>standalone.xml</strong> matches the worker IDs in the web server&#39;s <strong>workers.properties</strong>.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web server, application server, infrastructure</div> https://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server/revision/1Wed, 22 Feb 2017 20:20:28 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:33750534-fc61-48a1-b957-b400ea24b226Nick Vigilantehttps://community.appian.com/support/w/kb/297/kb-1072-requests-within-the-same-session-go-to-a-different-application-server#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 8:20:28 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>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).</p> <h2 id="cause">Cause</h2> <p>There is an improper configuration in <strong>standalone.xml</strong> or with session stickiness in the web server.</p> <h2 id="action">Action</h2> <ol> <li>Verify session stickiness is enabled in the web server. If using Apache, verify <code>worker.LoadBalancer.sticky_session=1</code> in <strong>httpd.conf</strong>, and if using IIS, verify <code>worker.wlb.sticky_session=1</code>in <strong>workers.properties</strong>.</li> <li>If using JBoss, verify each <code>node-id</code> in <strong>standalone.xml</strong> matches the worker IDs in the web server&#39;s <strong>workers.properties</strong>.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web server, application server</div>