IO10601: II4C LEAKS MEMORY WHEN CORRESPONDING LOG4J JAR IS NOT FOUND IN THE SYSTEM.

APAR status

• Closed as program error.

Error description

• II4C has upgraded log4j version in 8.4.1 and ICC still
  referencing old version of log4j. SO,when archiving from ICC
  CM8Connector is leaking memory and in 4 min we see
  Outofmemory error in ICC CM8Connector log.
  
  Since the II4C cmblogconfig.properties is configured to use
  log4j logging and the corresponding log4j jar has been updated
  in II4C and ICC is setting the classpath to use the old log4j is
  causing this memory leak.
  
  ICC will be fixing their code to use the updated log4j jar which
  is log4j1.2.15.jar.
  
  And II4C will change the code like if log4j classes not found
  then it will not try over and over instead it will cache after
  it's not found and use defalt logger.
  

Local fix

• Modify the cmblogconfig.properties to use default logger.
  DKLogManagerFactory =
  com.ibm.mm.sdk.logtool.DKLogManagerFactory_default
  

Problem summary

• The log4j class is loaded over and over again after the log4j
  class is not found.
  

Problem conclusion

• when an exception is caught because the log4j class could not be
  found, switch to the default logger in order to prevent
  additional log4j class loading issues.
  

Temporary fix

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

  II4C CM CONNECT

• Fixed component ID

  5724B43A1

Applicable component levels