IBM Support

PI65531: SCANNING OF A VS SOLUTION WITH VB.NET FILES THROWS A LOG4J NOT FOUND WARNING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • What's expected:
    
    IBM Security AppScan Source should be able to scan VS asp.net
    solution that contains both .js and .vb files successfully and
    returning satisfactory results.
    
    What's noticed:
    
    Customer has a Visual Studio solution of asp.net projects that
    contains several .js, .aspx and .vb files.  During scanning of
    the application when it completes scanning of one particular
    file called <filename>.vb it throws a warning like:
    
    log4j:WARN No appenders could be found for logger
    (net.htmlparser.jericho).
    log4j:WARN Please initialize the log4j system properly.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users may notice a warning about Log4J while scanning their  *
    * VB.Net code                                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When scanning VB.Net code using IBM Security AppScan Source, *
    * users sometimes may notice a warning like:                   *
    * log4j:WARN No appenders could be found for logger            *
    * (net.htmlparser.jericho).                                    *
    * log4j:WARN Please initialize the log4j system properly       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • On further investigation we noticed this warning may be a result
    of some required dependencies missing and this can be easily
    ignored because it just indicates the Logging system is not
    configured correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI65531

  • Reported component name

    SEC APPSCAN SRC

  • Reported component ID

    5724Z3400

  • Reported release

    902

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-08

  • Closed date

    2017-08-28

  • Last modified date

    2017-08-28

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSS9LM","label":"IBM Security AppScan Source for Automation"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"902","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
28 August 2017