IBM Support

PH01005: NULLPOINTEREXCEPTION WHEN APPLICATION PROVIDES A XALAN JAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When an application provides its own copy of Xalan.jar, that
    interacts with server use of its own copy of Xalan, which can
    cause a NullPointerException.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NullPointerException from             *
    *                      CommonExtensionsHelper occurs           *
    *                      when an application contains a copy of  *
    *                      Xalan.jar.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an application contains a copy of Xalan.jar, a step of
    processing application metadata can fail with a
    NullPointerException.
    When this problem occurs, the NullPointerException stack will
    include a listing of the class CommonExensionsHelper.
    

Problem conclusion

  • The problem occurred because code processing application
    metadata incorrectly used the application's class loader for a
    step of processing metadata.  That caused the application's
    copy of Xalan.jar to be used for the processing step instead
    of using the correct server internal class loader.
    
    The problem was fixed by changing the code step to use the
    correct server internal class loader.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs v8.5.5.15 and v9.0.0.11. 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

    PH01005

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-30

  • Closed date

    2019-02-11

  • Last modified date

    2019-02-11

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH01005

Modified date: 11 February 2019