NimbostratusI have this application hosted on the F5. The timeout set on the jboss/apache server end is 15 mins. Hence i set the timeout on the persistence profile to be 15 mins, but still it gets timeout before hand and user has to relogin. The problem does not come when the application is accessed direct from the server end.
CirrusWhat is the timeout set on TCP profile applied to the VS. I would create a custom tcp profile and change the timeout if needed.
Nimbostratuscurrently its the default one .
CirrusSo, if you need to change it to 15 minutes, then create a new tcp profile with idle timeout 15 minutes ( 900 seconds and apply that tcp profile to virtual server.
NacreousIf you are suffering from timeouts and the application expects the TCP session to remain open then configure a TCP profile with the appropriate timeout. Given this is a web application I am surprised this is needed. If you are able to watch a tcpdump while its running this will show you what is happening.
Essentially a web application usually will send additional http requests to get updates so TCP connection timeout is not usually an issue. If however you are using cookie pesistence, just make sure the clientside support cookies.
Nimbostratusdid all of that but still it kicks out sometime at 13 mins sometime before
CirrusThe timeout is idle timeout and is comes into play when the connection is idle. What kind of persistence profile are you using ?
AltostratusYou can try setting the idle timeout to indefinite.
1) create new tcp profile
2) set "indefinite" to Idle Timeout
3) set "indefinite" to Keep Alive Interval
Add this profile to your virtual and try it.
~ Gurus