IBM Support

IV91247: SUPPRESSING LOG ENTRIES MESSAGES FROM ALWAYS LOGGING IN THE LOG.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • EmailListnerTask and UploadFile classes are not using the
    standard logger this means that when this functionality is
    enabled the logs will have a potentially large number of
    unnecessary log entries.
    
    These log errors cannot be controlled. These entries will be
    numerous for organisations that upload large
    number of attachments.
    
    The following entries are samples from psdi.common.emailstner.
    EmailListnerTask.class
    
    /* 2345 */ System.out.println("ANTI-VIRUS SCANNER NOT CONFIGURED
    PROPERLY");
    
    In normal operation the following log messages will always be
    executed /* 2353 */  System.out.println("Calling Antivirus
    scanner...");
    
    The objective was to ensure that the system logs was not
    filling up with  large numbers of these log entries if someone
    enabled the anti-virus feature. We found this problem after I
    found a different problem/PMR about a missing system property
    that controlled this functionality.
    
    Looking at the code it is clear that the logs will be populated
    with log entries that can't be managed using the standard
    Maximo loggers so they can't be disabled.
    
    Steps to reproduce the problem
    ===============================
    
    This is based on code analysis after investigating a different
    problem raised as a separate PMR. The code appears to be
    executed when attachments are uploaded from the Email Listener
    Task code.
    
    It should be possible to replicate this by:
    
    1. Configure the Anti-virus scanner properties. (A subset of the
    messages can be seen by not setting the properties)
    
    2. Setting the mxe.doclink.isVirusScanEnabled property to true
    
    3. Sending an email with an infected attachment (some virus
    scanners
    have test files to confirm that the scanner is working)
    
    4. Watching the logs for standard output entries as per the
    examples above
    
    Product Version
    ===============
    TPAE 7506
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue does not affect any users. It only affects log    *
    * file data.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SUPPRESSING LOG ENTRIES MESSAGES FROM ALWAYS LOGGING IN THE  *
    * LOG                                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in EmailListnerTask.java
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV91247

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-05

  • Closed date

    2017-03-02

  • Last modified date

    2017-03-02

  • 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 SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2017