IBM Support

PM47655: A CLASSNOTFOUNDEXCEPTION MIGHT RESULT IF A CONTEXT CLASS LOADER OR URLCLASSLOADER IS USED WITH THE XML FEATURE PACK THIN CLIENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A ClassNotFoundException might be thrown for the
    class com.ibm.xml.logger.WSLoggerUtil if a context class
    loader has been specified in a program that uses the Thin
    Client for the Feature Pack for XML or if classes from the Thin
    Client are loaded using an instance of java.net.URLClassLoader.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the Feature Pack for XML Thin        *
    *                      Client is used in a program that        *
    *                      specifies a context class loader, or    *
    *                      if the program loads classes from the   *
    *                      Thin Client using an instance of a      *
    *                      URLClassLoader, a                       *
    *                      ClassNotFoundException might be         *
    *                      thrown for the class                    *
    *                      com.ibm.xml.logger.WSLoggerUtil.        *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this       *
    *                  APAR.                                       *
    ****************************************************************
    In trying to initializing its logging framework, the Feature
    Pack for XML Thin Client checks whether a user-specified
    logger has been requested, and if a user-specified logger has
    been requested, it attempts to load the implementation class
    for that logger.  If a context class loader has been
    specified, the Thin Client will use it to attempt to load the
    logger's implementation class.
    If no user-specified logger has been requested, the Thin
    Client attempts to use the class
    com.ibm.xml.xml.logger.WSLoggerUtil.  However, the Thin Client
    still attempts to use any context class loader to load that
    class, rather than using the class loader that loaded the
    logging framework itself.  If WSLoggerUtil is not available to
    be loaded by the context class loader, a
    ClassNotFoundException results.
    Finally, if the classes in the Thin Client are loaded using a
    URLClassLoader, a ClassNotFoundException results due to an
    explicit reference to the WSLoggerUtil class in the logging
    framework LoggerUtil class.  With other kinds of class
    loaders, that reference does not result in a
    ClassNotFoundException
    

Problem conclusion

  • The first problem was resolved by changing the logging
    framework to only use the context class loader in attempting
    to load a user-specified logger, not the default logger
    com.ibm.xml.xml.logger.WSLoggerUtil.  The second problem was
    fixed by changing the explicit references to
    com.ibm.xml.logger.WSLoggerUtil within the
    com.ibm.xml.logger.LoggerUtil class to references encoded in
    String values instead.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.2.  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 number

    PM47655

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-12

  • Closed date

    2011-10-18

  • Last modified date

    2011-10-18

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

    PM47427

  • 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

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021