Symptoms
iRule execution can block tmm from getting CPU cycles.
Impact
Logging shows now iRule perpetrator.
Conditions
when executing iRule TCL with e.g. a tight while loop, tmm will miss to sent its heartbeat. This change adds additional logging around this.
Fix Information
tmm will now log the following message should the configurable execution limit exceed:
notice tmm9[20262]: 01010338:5: Virtual /Common/http_respond iRule /Common/responder <HTTP_REQUEST> execution ran for 631 ticks (192.168.24.24:38169 -> 10.209.31.20:80 TCP)
notice tmm9[20262]: 01010029:5: Clock advanced by 632 ticks
