After our maintenance windows there was a problem to connect to appliance (TLS RC 493 and 5005 for initial handshake). So Guardium STAP for IMS continued to try to connect and caused a message flooding in our SYSLOG and an overload of our TCP/IP (related TCP/IP case was TS008437567).
It would be good to avoid this behaviour in case of failing connections, that caused a kind of internal denial of service in our system.
(Currently the behavior of S-TAP IMS is normal under this situation; STAP made the connection, but due to an AT-TLS issue, communications were not successful. Labor said that within the current design of the IMS and Dataset STAPs, any retry counter or delay values would not be in effect due to the connection actually having been made.)
Do not place IBM confidential, company confidential, or personal information into any field.