Loading...
Loading...
TMM cores with the log message 'panic: Invalid Tcl recursion' and a stack trace.
When LB::prime command executes, the queued messages are processed, resulting in a core as these messages are not using the correct Tcl context. Rarely, a crash causes the pool members go down.
This crash rarely occurs when the following conditions are met. 1. SIP on TCP profile. 2. Triggering LB::Prime irule every few seconds on CLIENT_ACCEPTED event. 3. Server-side congestion due to a large amount of traffic. 4. Large queues of undelivered proxied messages.
None.
When you use the LB::prime pool command, the system now flushes the queue, so server-side congestion no longer prevents the messages from being processed.
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.