Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
12.0.0, 11.6.0 HF6, 11.5.4
Opened: May 18, 2015
In certain scenarios, session entries may not be refreshed when the TMM that owns the entry is used to process the connection.
Different TMMs may behave differently and cause confusion when using the session table.
When the TMM owning the session entry is a different one to the TMM handling the connection and the entry is retrieved, for example via irule, "session lookup uie"; the timeout will be extended. When the TMM owning the entry and the one handling the connection is the same, then the entry may not have its timeout changed and lead to premature removal.
Session table entries now consistently get their timeout values touched in all scenarios.