Posted: 26 Jan 2016 9:48 EST Last activity: 2 Feb 2016 11:37 EST
Pega/Chordiant network presents applet and network load-balancer sticky sessions
Should the applciation load-balancer sticky session timeout agree with the application session timeout with regards to the network presents applet? For example, if the servlet session timeout is set to 720 minutes should the load-balancer set its session timeout to 720 minutes as well?
If your question is about the idle connection timeout of the load balancer, Below is what my understanding is: For each request that a client makes through a load balancer, the load balancer maintains two connections. One connection is with the client and the other connection is to the back-end instance. For each connection, the load balancer manages an idle timeout that is triggered when no data is sent over the connection for a specified time period. After the idle timeout period has elapsed, if no data has been sent or received, the load balancer closes the connection.
Suppose the idle timeout is set to 60 seconds for both connections. If an HTTP request doesn't complete within the idle timeout period, the load balancer closes the connection, even if data is still being transferred. You can change the idle timeout setting for the connections to ensure that lengthy operations, such as file uploads, have time to complete.
So Ideally you should configure the idle connection timeout of the load balancer more than the application session timeout.
If you are referring anything different than the above mentioned idle connection timeout of the load balancer, Could you please elaborate more? I am not sure if there is any different timeout for the session stickiness configurations. Are you referring to Duration-Based Session Stickiness?
Posted: 6 years ago
Posted: 2 Feb 2016 8:05 EST
Rich Lanzillo (RichardL4784)
CNO Financial Group
CNO Financial Group
I think you are confusing two separate processes. I am referring to the load-balancer sticky session, which is separate from a the individual HTTP request timeout(usually a minute or two). I believe this what you start out defining in the first paragraph by referencing an individual connection, what I am referring to is many connections over a period of time.
Application sessions and load-balancer sticky sessions generally run from 30 minutes to a full day depending of the circumstances.
Foundation Server needs stickty sessions due to the network presents applet, the question is, does the load-balancer sticky session need to the same as the application servers sessions values?
A Cisco load-balancer: ((config-sticky-ip)# timeout 720)
Your Advisor web.xml: <session-timeout>720</session-timeout>
Is this required for your application to behave properly?