Forum Discussion

epaalx's avatar
epaalx
Icon for Cirrus rankCirrus
Dec 14, 2016

Clarification of OneConnect profile's "idle-timeout-override"

Regarding "idle-timeout-override", states

 

"The Idle Timeout Override setting specifies the number of seconds that a connection is idle before the connection flow is eligible for deletion. You can use this setting to override the protocol profile time-out and increase the time-out value for connections once they are pooled for re-use."

 

My question: does the this override the (protocol profile) idle-timeout of both the original connection and reused connections, or, only the latter?

 

application delivery
LTM

4 Replies

Sort By
  • Kai_Wilke's avatar
    Kai_Wilke
    Icon for MVP rankMVP
    Dec 14, 2016

    Hi Epaalx,

     

    a new connection will be created and will use the protocol-specific idle timeout settings. If OneConnected is active and the connection is marked for reuse (aka. ONECONNECT::reuse enable), the connection will be put into your OneConnect pool. The Idle Timeout Override setting may then apply new timeout values to this connection...

     

    If another connection will be created the LTM may create a new connection (if OneConnect session pool is currently busy) or it will reuse a previous OneConnect connection with the now changed Idle Timeout Override settings.

     

    Cheers, Kai

     

  • 3junior_134880's avatar
    3junior_134880
    Icon for Nimbostratus rankNimbostratus
    May 04, 2017

    Hi,

     

    Can I use "Idle Timeout Override" to kill an existing connection? max-age will only not allow new connection to server. I am looking to kill existing connection after x amount of time without touching tcp profile

     

    • Vijay_E's avatar
      Vijay_E
      Icon for Cirrus rankCirrus
      May 04, 2017

      I think the TCP profile's idle timeout takes precedence. I am not 100% sure but you can sure try it out.