IBM Support

PI67363: APPLICATION SERVER STARTUP LOG4J ERROR OUTPUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following error is seen in logs during startup of
    Application Server 9.0 after fresh install
    
    SystemErr     R ERROR StatusLogger Log4j2 could not find a
    logging implementation. Please add
    log4j-core to  the classpath. Using SimpleLogger to log to the
    console
    

Local fix

  • No work around. The error is safe to ignore.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  who use the Knowledge Center in the Admin   *
    *                  Console.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Upon starting the server, a LOG4J error *
    *                      was found in the systemerror log and    *
    *                      extraneous info messages are in the     *
    *                      systemout log.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the user starts a server a log4j error is found in the
    SystemErr.log file and extraneous KC info messages are found in
    the SystemOut.log. The log4j was related to a missing jar file
    in
    KC and the extra log messages were due to the KC log settings.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI67363

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-10

  • Closed date

    2017-06-05

  • Last modified date

    2017-06-05

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
13 October 2021