Hello Rich,

Thanks for raising the query. While I am looking into this, could you please confirm the Foundation Server version used at your end?

Regards,

Rincy

Hi Rich,

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?

Regards,
Raghav