Forum Discussion
hc_andy_35682
Mar 24, 2010Nimbostratus
I believe I've been able to fix this now.
I think what is happening is that once a connection is intiated between the client > LTM > server, the LTM keeps track of two different idle time outs.
1/ fastl4 profile - idle timeout 300 sec (to do with keeping the tcp connection /socket alive )
2/ source address persistence - idle timeout 180sec (to do with keeping the session alive )
I believe webmail (horde) has a feature where every 300sec it renews/updates the session id. We've noticed that every 5mins, the URL refreshes and contains a new "uniq=14423679ba97d91" string at the end of it.
So at the 300sec mark, webmail tries to renew /update the session id but the LTM has already trashed the session id information because it's got a source address persistence idle timeout of 180sec. And so because there is no matching session id found on the LTM, webmail ends the session and logs out the user.
To fix this, we need to ensure that the source address persistence idle timeout is greater than 300 sec which I've set to 360 sec. Testing seems to indicate this is working.