Option 1: Disable sticky sessions for the APSV transportThis means the Load Balancer will check the status of PAS instances and Clustering handles the session replication.
The Tomcat servlet container in PASOE does not allow web applications to change a session to a sticky session.
Change the following from true to false in the worker.properties file:
worker.lb.sticky_session=false
worker.lb.sticky_session_force=false
Option 2: use sticky sessions for the APSV transport but don't force them This means if the one PAS instance goes down, the Load Balancer will recognize this and move the request on to another PAS instance and Clustering handles the session replication.
Change the following from true to false in the worker.properties file:
worker.lb.sticky_session=true
worker.lb.sticky_session_force=false