Bug ID 712489: TMM crashes with message 'bad transition'

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
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, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 14.0.0,,,,,, 14.1.0,,,,,,, 15.0.0

Opened: Mar 28, 2018
Severity: 3-Major


TMM crashes under a set of conditions in which the system detects an internal inconsistency. The system posts an error similar to the following in the LTM and TMM logs: crit tmm[18755]: 01010289:2: Oops @ 0x2285e10:5157: bad transition


TMM crashes and restarts. Traffic disrupted while tmm restarts.


Conditions that cause this to happen are not predictable, but these might make it more likely: -- FastL4 virtual server and HTTP are configured -- db variable tmm.oops set to 'panic'. -- Client sends three GET requests at once, and then closes the connection after a few seconds. -- The server sends a partial 'Connection: close' response.



Fix Information


Behavior Change