IT29131: MEMORY LEAK CAUSING THE PRODUCT TO CRASH

APAR status

• Closed as program error.

Error description

• Memory Leak causing the product to crash
  

Local fix

• NA
  

Problem summary

• A slow memory leak in the log4j2 logging subsystem led to an
  OutOfMemory (OOM) exception crash of the SSP engine after
  several weeks. Analysis of  the heap dumps showed the following:
    The class
  "org.apache.logging.log4j.core.appender.AbstractManager"
    occupies 1,904,050,896 (89.23%) bytes. The memory is
  accumulated in one
    instance of "java.util.HashMap$Node[]".
  For each new session in which logging was enabled, the logging
  system was adding a new appender to write to the log file, even
  though in most cases,  one already existed for that file.
  

Problem conclusion

• Corrected the logic which decided whether a new logging
  appender was required so that duplicate entries would not longer
    accumulate and cause an OOM exception.
  

Temporary fix

• SSP3432 iFix 4 Plus Build 306
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels