Forum Discussion
Jonathan_c
Cirrus
CirrusAPM session inactivity timeoute VS. TCP idle timout
Hi,
I'm confused by these two settings and the relation between them.
I have a VS with client and server TCP profile which has 600 seconds Idle Timeout (the keep alive interval is 1800 seconds, so I guess it's not a factor here).
This VS as APM profile with a Inactivity Timeout setting of 900 seconds.
What exactly is the relation between these two settings?
Does it mean that APM sessions will never reach 900 seconds and users will be disconnected after 600 seconds?
Thanks
So APM works on logged in sessions, and users but from that the application might open many tcp connections to service that session.
So really its contextualisation of what APM is doing (Access) and ltm is doing (connections).So your timer question, many tcp connections may have been opened and closed but you have never logged out of APM therefore your session is still open.
Hope that helps, i've had to fault find APM one or two times and its always diffcult trying to get it all to line up.
But that's more the application and how it works rather than the f5 APM module.
So APM works on logged in sessions, and users but from that the application might open many tcp connections to service that session.
So really its contextualisation of what APM is doing (Access) and ltm is doing (connections).So your timer question, many tcp connections may have been opened and closed but you have never logged out of APM therefore your session is still open.
Hope that helps, i've had to fault find APM one or two times and its always diffcult trying to get it all to line up.
But that's more the application and how it works rather than the f5 APM module.
