Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.5.0, 11.4.1 HF9
Opened: Jul 17, 2013
Related AskF5 Article: K15078
The errors caused could be anything from invalid data being returned by a different iRule command to an iRule error being raised (which would normally kill the flow), with the latter possibly logging a message in /var/log/tmm* which looks like "Received bad req_id: (0000004a00000072 != 0000000000000000)" depending on the exact command.
Connections being reset, or other problems resulting from bad data being returned from iRule commands.
If a session command runs and is followed by some other iRule command which uses the session DB, then some problem is likely to happen.
Replace session iRule commands with table iRule command equivalents.
Errors no longer happen when using session iRule commands.