IJ43547: LOGGERS FAIL TO WRITE LOG ENTRY FOR AUTOMATION SCRIPTS AFTER LOG4J UPGRADE

APAR status

• Closed as program error.

Error description

• Problem description:
  
  Loggers fail to write log entry for automation scripts after
  log4j upgrade
  
  Steps to reproduce:
  
  Create a very simple custom autoscript:
  
  from psdi.util import HTML
  from psdi.util.logging import MXLogger
  from psdi.util.logging import MXLoggerFactory
  
  myLogger =
  MXLoggerFactory.getLogger("maximo.application.WOTRACK")
  myLogger.error("script TMP called ERROR")
  myLogger.info("script TMP called INFO")
  myLogger.debug("script TMP called DEBUG")
  myLogger.debug("Mbo is " + mbo.getString("WONUM") + " and status
  " + mbo.getString("STATUS"))
  
  ====
  
  Launchpoint information:
  
  Create a launch point on the description attribute on the
  WORKORDER object.
  
  It should be triggered on the validate action
  
  
  ====
  
  Logging information:
  
  application logger - INFO
  child logger WOTRACK - DEBUG
  apply settings etc
  
  
  ====
  
  Create a Wor Order
  
  Enter a description
  
  Move to a different field to trigger the validate method
  
  Check the logs to confirm that the log entries are generate
  correctly
  
  
  Current results:
  
  
  Some of the log entries are not being logged
  
  Expected results:
  
  
  All the messages should be logged to SystemOut.log
  
  
  Environment:
  
  Tivoli's process automation engine 7.6.1.2
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IJ43547 LOGGERS FAIL TO WRITE LOG ENTRY FOR AUTOMATION       *
  * SCRIPTS AFTER LOG4J UPGRADE                                  *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 8.x Product
  

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels