connection behavior with or without oneconnect

Just wonder do you mean Keep Alive Interval or Idle Timeout from TCP profile? I guess that for server side connections with OneConnect applied what is used to end connection are settings from OneConnect profile (Maximum Age, Maximum Reuse) not from TCP profile - but may be wrong, I am not really sure what Idle Timeout Override (in OneConnect) setting is changing in this equation. Or maybe it's like that: 1. Maximum Age (OC profile) specifies how long server side connection can be used, after specified number of seconds connection is closed if it's Idle Timeout in TCP profile was not exceeded 2. If Maximum Age did not pass but Idle Timeout in TCP connection expired then server connection is closed not honoring Maximum Age setting 3. When it's necessary to have different Idle Timeout for server side (using OC) for setting in TCP profile (and used in this case for client side connections) then it can be changed using Idle Timeout Override in OC profile Is above makes sense? Piotr