Bug ID 459382: SASP monitor does not reconnect to the Group Workload Manager (GWM) server in case the server resets the TCP connection

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:

Fixed In:
10.2.4 HF12

Opened: Apr 28, 2014

Severity: 2-Critical

Related Article: K17060


The GWM server can reset the TCP connection to the SASP monitor multiple times. In this scenario, the monitor does not re-attempt connecting the server. This results in incorrect status reporting of pool members and hence data traffic may be impacted.


This could possibly affect data traffic sent to the servers as the SASP monitor is no longer connected to the GWM server.


The GWM server sends TCP reset to the SASP monitor TCP connection.


This issue has no workaround at this time.

Fix Information

The GWM server may reset the TCP connection to the SASP monitor during the registration or deregistration of group members at startup. If this happens than the monitor shall reconnect to the GWM server.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips