IBM Support

PI77666: THREAD CONTEXT CLASSLOADER NOT SET UP CORRECTLY DURING CDI BOOTSTRAP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During CDI bootstrap, the Thread Context Class Loader (TCCL) on
    WAS v9 is not set up correctly. This leads to
    ClassNotFoundExceptions when trying to perform various
    initialization steps within CDI extensions
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: During CDI bootstrap, the Thread        *
    *                      Context Class Loader (TCCL) on          *
    *                      WAS v9 is not set up correctly. This    *
    *                      leads to                                *
    *                      ClassNotFoundExceptions when trying to  *
    *                      perform various                         *
    *                      initialization steps within CDI         *
    *                      extensions                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During CDI bootstrap, the Thread Context Class Loader (TCCL)
    should be set to the classloader of the module that is being
    bootstrapped. This was not occurring leading to problems
    attempting to use the TCCL in a CDI extension and compatibility
    issues with Apache DeltaSpike.
    

Problem conclusion

  • New code was added to set the Thread Context ClassLoader.
    Because of technical limitations this code only sets a TCCL when
    there is only one module in the application. E.G. an EAR file
    with one only WAR inside it.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.5.  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

    PI77666

  • 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

    2017-03-06

  • Closed date

    2017-08-10

  • Last modified date

    2017-08-10

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022