Troubleshooting load balancing issues


This topic explains the load balancing issues and their workarounds.

Resolution for load balancing issues

Symptom

Action

Reference

The following error message is displayed on the UI:

Failed to get socket bind address for application server : "serverHostname" due to " <cause of error>

Enter a valid load balancer server name when you set the following parameter by using the set command in the blasadmin utility:

set AuthServer LoadBalancerHosts "<loadBalancerhostname1>,<loadBalancerhostname2>"

The following error message is logged in the appserver.log file located in the application server installation directory for the specific deployment:

Session with session id: %s does not exist in database if user requested using an improper session_id.

Enter a valid session ID in the REST API syntax.

The following warning message is logged in the appserver.log file located in the application server installation directory for the specific deployment:

Unable to retrieve value for blasadmin "loadBalancerHosts hence load balancer is not enabled.

Set the LoadBalancerHosts parameter by using the set command in the blasadmin utility.

If you try to log in after the session has expired, the following error message is logged in the restapi_<>.log file:

[ERROR] [::] Error occurred while authenticating api keysInvalid sessionId: active session was not found. Please login
[ERROR] [::] Error occurred while authenticating api keysInvalid sessionId: active session was not found. Please login

Log in to the session again.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*