Last Modified: Jan 11, 2021
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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
12.0.0, 11.6.0 HF5, 11.5.3
Opened: Aug 04, 2014
Related AskF5 Article: K16957
Certain conditions might produce error messages similar to the following in the core file/tmm.log: -- RVAvpBigIP01 notice RIP=0x8cc872 -- RVAvpBigIP01 notice session_process_pending_event_callback ERROR: could not send callback to 192.168.96.27:504 - 192.168.96.28:443 ERR_NOT_FOUND.
Traffic disrupted while tmm restarts.
This occurs because of a race condition, one between the HTTP and APM-related profiles, for example, during which an APM-profile-related action completes after the HTTP-profile closes the connection. Note: Logs that occur without a core are not a symptom related to this issue.
The race condition that occurred has been fixed, so no APM-profile-related actions complete after the HTTP-profile closes the connection.