IBM Support

PH01108: NPE IN CDI WELD WHEN MIGRATING FROM WEBSPHERE JAVA 6 TO JAVA 8

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customers migrating their application running on WebSphere v7
    using JDK v6 may run into CDI issues when rebuilding their
    applications using WebSphere v9 using Java 8.
    
    
    [7/25/18 9:43:00:062 CST] 0000007b CDIDeployment > <init> Entry
    java.lang.NullPointerException
    at
    com.ibm.ws.cdi.impl.weld.BeanDeploymentArchiveImpl.createInjecti
    onTargetsForJEEComponentClasses(BeanDeploymentArchiveImpl.java:9
    10)
    at
    com.ibm.ws.cdi.impl.weld.WebSphereCDIDeploymentImpl.validateJEEC
    omponentClasses(WebSphereCDIDeploymentImpl.java:825)
    at
    com.ibm.ws.cdi.impl.CDIContainerImpl.startInitialization(CDICont
    ainerImpl.java:157)
    at
    com.ibm.ws.cdi.classic.CDIRuntimeImpl.applicationStarting(CDIRun
    timeImpl.java:352)
    at
    com.ibm.ws.cdi.classic.CDIRuntimeImpl.start(CDIRuntimeImpl.java:
    444)
    at
    com.ibm.ws.cdi.classic.CDIRuntimeImpl.stateChanged(CDIRuntimeImp
    l.java:581)
    

Local fix

  • Disable CDI
    
    Java custom properties and manifest attributes are introduced
    to disable CDI processing steps:
    
            Name: com.ibm.ws.cdi.enableCDI
            Allowed Values: true, false
            Default Value: true
            Description: By setting the com.ibm.ws.cdi.enableCDI
    custom property to false, all CDI steps are disabled. Set the
    value to false if no CDI is needed on the server level.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Null JEEComponentClasses were being     *
    *                      registered as CDI Beans                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When buildig it's internal metadata null was being provided to
    CDI as a JEEComponentClass. This resulted in a Null Pointer
    Exception when CDI processed this bean.
    

Problem conclusion

  • When CDI builds adds a JEEComponentClass to it's inernal
    metadata it now filters out null.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.10. and liberty 18.0.0.3 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

    PH01108

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-31

  • Closed date

    2018-10-25

  • Last modified date

    2018-10-25

  • 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

  • R900 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
08 September 2021