PI07534: ILLEGALARGUMENTEXCEPTION OCCURS WHEN LOGGER CREATED IS NOT AN INSTANCE OF WSLOGGER.

7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When a logger getting created is not an instance of
  WsLogger(which is WebSphere own Logger), fails with the
  following Exception.
  
  Caused by: java.lang.IllegalArgumentException: Logger passed as
  argument to setAttributes must be a named logger
   at
  com.ibm.ws.logging.LoggerHelper.setAttributes(LoggerHelper.java:
  192)
   at com.ibm.ws.logging.WsLogger.<clinit>(WsLogger.java:97)
   at java.lang.J9VMInternals.initializeImpl(Native Method)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
   at
  com.ibm.ws.logging.WsLoggerFactoryImpl.createWsLogger(WsLoggerFa
  ctoryImpl.java:79)
   at
  com.ibm.ws.bootstrap.RASDelegator.createWsLogger(RASDelegator.ja
  va:74)
   at
  com.ibm.ws.bootstrap.WsLogManager.getLogger(WsLogManager.java:21
  8)
   at java.util.logging.Logger.getLoggerWithRes(Logger.java:350)
   at java.util.logging.Logger.getLogger(Logger.java:376)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Version 7                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a logger being created is not      *
  *                      an instance of WsLogger (which is       *
  *                      Application Server's own Logger), it    *
  *                      fails with Exception                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application tries to register a logger, if it is not an
  instance of WsLogger (which is WebSphere Application Server's
  own implementation of Logger),then an IllegalArgumentException
  is thrown.
  

Problem conclusion

• A check has been added to see if the new logger registered is
  an instance of WsLogger. If it is not, then it will not
  throw any exception. This fix is already present in Version
  8.0 and above.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.33.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP