KB-1422 How to determine which application server node is hosting the current user session

Parmida Borhani — Thu, 03 Jan 2019 23:37:27 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/3/2019 11:37:27 PM

Purpose

Sometimes it may be necessary to determine which application server node a session is hitting for troubleshooting purposes. This article outlines how to do this for an environment with multiple application servers.

Instructions

Each application server will have an instance-id/node-name that uniquely identifies that instance. If using JBoss, navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. If using Tomcat, navigate to setenv.bat|sh file and find the line where DjvmRoute is defined.

Chrome/Firefox

Visit the site URL to load the login page.
Press F12 to open Chrome/Firefox Developer Tools.
In Chrome, click “Application” > “Cookies” > <site-url> > “JSESSIONID”. In Firefox, click "Storage" > "Cookies" > <site-url> > "JSESSIONID".
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Internet Explorer

Visit the site URL in a private browsing session.
Press F12 and click on the 'Network' tab.
Click on the green play button to start capturing network traffic, and reload the page.
Once the page is done loading, click on the red stop button, and then click on the Details tab. You should see the JSESSIONID stored in the Cookie field.
Take note of the node ID, then close the window and try these steps again until you get the correct node ID.

Note: This approach (modified slightly for the browser) will work for the Chrome and Firefox as well.

Affected Versions

This article applies to Appian environments with multiple application servers.

Last Reviewed: January 2019

Tags: Tomcat, browser, application server, how-to, jboss

KB-1422 How to determine which application server node is hosting the current user session

Parmida Borhani — Thu, 03 Jan 2019 23:33:46 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 1/3/2019 11:33:46 PM

Purpose

Instructions

Chrome/Firefox

Visit the site URL to load the login page.
Press F12 to open Chrome/Firefox Developer Tools.
In Chrome, click “Application” > “Cookies” > <site-url> > “JSESSIONID”. In Firefox, click "Storage" > "Cookies" > <site-url> > "JSESSIONID".
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Internet Explorer

Visit the site URL in a private browsing session.
Press F12 and click on the 'Network' tab.
Click on the green play button to start capturing network traffic, and reload the page.
Once the page is done loading, click on the red stop button, and then click on the Details tab. You should see the JSESSIONID stored in the Cookie field.
Take note of the node ID, then close the window and try these steps again until you get the correct node ID.

Note: This approach (modified slightly for the browser) will work for the Chrome and Firefox as well.

Affected Versions

This article applies to Appian environments with multiple application servers.

Last Reviewed: January 2019

Tags: Tomcat, application server, how-to, jboss

KB-1422 How to determine which application server node is hosting the current user session

Jordan Horwat — Thu, 25 Oct 2018 09:36:01 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 10/25/2018 9:36:01 AM

Purpose

Instructions

Each application server will have an instance-id/node-name that uniquely identifies that instance.
If using JBoss, navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. If using Tomcat, navigate to setenv.bat|sh file and find the line where DjvmRoute is defined.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to Appian environments with multiple application servers.

Last Reviewed: October 2018

Tags: Tomcat, application server, how-to, jboss

KB-1422 How to determine which application server node is hosting the current user session

Jordan Horwat — Thu, 25 Oct 2018 09:34:50 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 10/25/2018 9:34:50 AM

Purpose

Instructions

Each application server will have an instance-id/node-name that uniquely identifies that instance.
If using JBoss, navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. If using Tomcat, navigate to setenv.bat|sh file and find the line where DjvmRoute is defined.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple application servers.

Last Reviewed: October 2018

Tags: Tomcat, application server, how-to, jboss

KB-1422 How to determine current JBoss node

Parmida Borhani — Fri, 31 Aug 2018 00:45:40 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 8/31/2018 12:45:40 AM

Purpose

Sometimes it may be necessary to determine which JBoss node a session is hitting for troubleshooting purposes. This article outlines how to do this for environments with multiple JBoss application servers.

Instructions

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple JBoss application servers.

Last Reviewed: November 2017

Tags: application server, how-to, jboss

KB-1422 How to determine current JBoss node

Parmida Borhani — Tue, 19 Dec 2017 16:22:08 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 12/19/2017 4:22:08 PM

Purpose

Instructions

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple JBoss application servers.

Last Reviewed: November 2017

Tags: application server, how-to

How to determine current JBoss node

Parmida Borhani — Sun, 19 Nov 2017 22:22:16 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 11/19/2017 10:22:16 PM

Sometimes it may be necessary to determine which JBoss node a session is hitting.

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple JBoss application servers.

Last Reviewed: November 2017

Tags: application server, how-to

KB-1422 How to determine current JBoss node

Parmida Borhani — Sun, 19 Nov 2017 17:25:50 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 11/19/2017 5:25:50 PM

Sometimes it may be necessary to determine which JBoss node a session is hitting.

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple JBoss application servers.

Last Reviewed: November 2017

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Thu, 16 Nov 2017 16:57:07 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 11/16/2017 4:57:07 PM

Sometimes it may be necessary to determine which application server node a session is hitting.

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

Affected Versions

This article applies to environments with multiple application servers.

Last Reviewed: November 2017

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Wed, 15 Nov 2017 19:20:57 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 7:20:57 PM

Sometimes it may be necessary to determine which application server node a session is hitting.

Each application server will have an "instance-id" in standalone.xml that uniquely identifies each JBoss instance. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node that was noted in step 1, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

This article applies to environments with multiple application servers.

Last Reviewed: November 2017

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Mon, 06 Nov 2017 17:56:45 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/6/2017 5:56:45 PM

Sometimes it may be necessary to determine which application server node a session is hitting.

Each application server will have an "instance-id" of its own defined in standalone.xml. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

This article applies to environments with multiple application servers.

Last Reviewed: November 2017

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Mon, 06 Nov 2017 17:50:52 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/6/2017 5:50:52 PM

Sometimes it may be necessary to determine which application server node a session is hitting.

Each application server will have an "instance-id" of its own defined in standalone.xml. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

This article applies to environments with multiple application servers.

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Mon, 06 Nov 2017 17:49:34 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 11/6/2017 5:49:34 PM

Sometimes it may be necessary to determine which application server node a session is hitting.

Each application server will have an "instance-id" of its own defined in standalone.xml. Navigate to the standalone.xml file for the application server node you would like to hit and find the line where "instance-id" is defined. Note the value.
Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node, double click the value and delete the contents.
Refresh the page and repeat the above steps until you get to the desired node ID.

This article applies to environments with multiple application servers.

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Mon, 06 Nov 2017 17:43:26 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/6/2017 5:43:26 PM

Sometimes it may be necessary to determine which application server node a user is on.

Visit the site URL to load the login page.
Using Chrome, press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
Mouse over the value of JSESSIONID and you will see an alphanumeric string which ends with a node number.
If you are not on the desired application server node, double click the Value field and delete the value.
Refresh the page and repeat the above steps until you get the desired node ID.

This article applies to environments with multiple application servers.

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Mon, 06 Nov 2017 17:36:51 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/6/2017 5:36:51 PM

Sometimes it may be necessary to determine which application server node a user is on.

Visit the site URL to load the login page.
On Chrome press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
On the server with the compressed logs, find its node ID using value of instance-id from the output below:
grep instance-id /usr/local/appian/ae/jboss1/standalone/configuration/standalone.xml
In Chrome, right click and delete the value if it does not match the JSESSION ID of the server.
Refresh the page and repeat the above steps until you get the desired node ID.

This article applies to environments with multiple application servers.

Tags: application server, how-to

How to determine current application server node

Parmida Borhani — Fri, 03 Nov 2017 01:42:32 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 11/3/2017 1:42:32 AM

This article applies to Appian Cloud sites with multiple application servers.

Visit the site URL to load the login page.
On Chrome press F12 to open developer tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
On the server with the compressed logs, find its node ID using value of instance-id from the output below:
grep instance-id /usr/local/appian/ae/jboss1/standalone/configuration/standalone.xml
In Chrome, right click and delete the value if it does not match the JSESSION ID of the server.
Refresh the page and repeat the above steps until you get the desired node ID.

Tags: application server

How to determine current application server node

Parmida Borhani — Thu, 02 Nov 2017 21:49:33 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 11/2/2017 9:49:33 PM

This article applies to Appian Cloud sites with multiple application servers.

Visit the site URL to load the login page.
On Chrome press F12 to open Developer Tools.
Click “Application” > “Cookies” > <site-url> > “JSESSIONID”.
On the server with the compressed logs, find its node ID using value of instance-id from the output below:
grep instance-id /usr/local/appian/ae/jboss1/standalone/configuration/standalone.xml
In Chrome, right click and delete the value if it does not match the JSESSION ID of the server.
Refresh the page and repeat the above steps until you get the desired node ID.

Tags: application server, how-to