Bug ID 612694: TCP::close with no pool member results in zombie flows

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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

Fixed In:
13.0.0, 12.1.2 HF1, 11.6.2

Opened: Aug 25, 2016
Severity: 3-Major
Related AskF5 Article:
K70557109

Symptoms

'tmsh show sys conn all-properties' shows connections whose idle time exceeds the timeout.

Impact

Connection does not tear itself down.

Conditions

There is no pool member, and a TCP::close iRule activates (typically after a TCP::respond).

Workaround

Make TCP::close conditional on pool failure, and rely on the pool failure to RST the connection rather than perform a clean TCP close.

Fix Information

The system now properly handles TCP teardown when TCP::close has already torn down the rest of the stack.

Behavior Change