IT24941: A LOG TARGET STATUS MEMORY VALUE IS NOT CORRECT, ALWAYS BEING TOO LOW
Fixes are available
Closed as program error.
The user observed slowly increasing memory usage but struggled to pinpoint which part of configuration or traffic caused this. It turned out that having log target Identical Event Detection enabled, especially in combination with log target type syslog-tcp, did hold memory for a long time, as in this specific scenario many unique log records got created and where hold even beyond the Identical Event Detection timeout. It turned out this part of hold memory is not captured in the log target status provider, so customer could not pinpoint this specific log target to be the driver.
Either shortly disable/enable the log target object to reclaim hold memory, or do not use Identical Event Detection (a preferred practice anyway to safe resources on DataPower), or more specifically don't use Identical Event Detection if the log target type is syslog-tcp.
The logging target status might not reflect actual memory used.
Fix is available in 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124 and 126.96.36.199 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels