IBM Support

IJ51008: UNINTENTIONAL DEBUG LOGS ON WOACTIVITY IN SYSTEMOUT LOG

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The Maximo application is generating a high volume of DEBUG
    logs; typically generating 20GB of logs daily.
    All Maximo root loggers/loggers are at INFO level or ERROR level
    and this is also confirmed by the following SQL statements:
    
    Select * from MAXLOGGER;
    
    Select * from MAXLOGAPPENDER;
    
    In a non-replicated issue environment, the logger is
    instantiated by the slf4j-api lib and  set to level INFO, unlike
    the environment where the DEBUG mode logger is instantiated by
    the mas-data-dictionary-lib-1.0.0 lib which is at DEBUG level.
    
    The issue is two-fold:
    
    
    1) Maximo FldWOEstTotalCost.java has three debug statements
    that always get submitted and need to be wrapped with an
    isDebugEnabled() check
    
    		myLogger.debug("WOTOTAL: entered
    FldWOEstTotalCost.initValue");
    		myLogger.debug("WOTOTAL: EstTotalCost init'ed to " +
    totalTotal);
    		myLogger.debug("WOTOTAL: exiting
    FldWOEstTotalCost.initValue");
    
    
    2) mas-data-dictionary-1.0.0.jar contains a Log4j.properties
    file that when loaded prior to Maximo Server start up will
    override the Maximo Logging rootLogger and can override the Log
    Level of all Maximo logging.
    
    
    The Log4j.properties file should be removed from the jar file.
    
    
    
    STEPS TO REPRODUCE: N/A
    
    RESULTS:
    High volume of logs generated at DEBUG level by lib files.
    
    EXPECTED RESULTS:
    
    No DEBUG logging should be generated beyond what is configured
    via the Maximo  Loggers application
    
    PRODUCT VERSION:
    7.6.1.3
    

Local fix

  • Developer to provide fix
    

Problem summary

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ51008

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-26

  • Closed date

    2024-05-30

  • Last modified date

    2024-05-30

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 May 2024