Bug ID 457934: SSL Persistence Profile Causing High CPU Usage

Last Modified: Jul 18, 2026

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 hf1, 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.1 hf10, 11.5.1 hf11, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.2

Opened: Apr 18, 2014

Severity: 3-Major

Related Article: K16178

Symptoms

Some connections through a virtual server using SSL persistence hang and cause a high CPU condition in tmm.

Impact

Large increase in CPU usage on the box and a percentage of SSL connections through the virtual server are delayed and eventually reset

Conditions

This occurs only when SSL persistence is configured as the default persistence profile, and there is a fallback profile of either source_addr or dest_addr.

Workaround

None.

Fix Information

SSL Persistence Profile now operates correctly, and does not cause high CPU usage.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips