Bug ID 720041: CPU Utilization Increases when SSL Session ID Persistence is enabled with HTTP/2 Profile

Last Modified: Dec 20, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 13.1.3,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,,, 14.1.2,,,, 15.1.0

Opened: May 14, 2018
Severity: 4-Minor


When an HTTP/2 profile is applied to a virtual server, and SSL Session ID (SSID) persistence is enabled on the virtual server, CPU utilization jumps to 80%. TMM is found to consume most of the CPU cycles.


TMM consumes most of the CPU, and CPU utilization becomes 80%.


-- An HTTP/2 VIP has a pool containing multiple members. -- A OneConnect profile is used (to force proxy_connect on every request). -- A client makes multiple requests on the same HTTP/2 connection (e.g., curl with nghttp support).


To prevent this issue, add a new SSL persistence profile with 'match-across-virtuals enabled'.

Fix Information


Behavior Change