PI67363: APPLICATION SERVER STARTUP LOG4J ERROR OUTPUT

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

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

• The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.4.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R900 PSY

     UP