IBM Support

PI85587: JAVA.LANG.NULLPOINTEREXCEPTION WHEN STARTING AN EBA CONTAINING AN EJB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During startup, application fails with WSVR0067E: EJB container
    caught java.lang.NoClassDefFoundError:
    com.ibm.websphere.models.extensions.helpers.impl.PMEEJBJarExtens
    ionHelperImpl (initialization failure) with linked exception of
    Caused by: java.lang.NullPointerException
     at
    m.ibm.websphere.models.extensions.pmeext.commonext.serialization
    .DocumentRootUtil.createDocumentRootEClass(DocumentRootUtil.java
    : 60)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of OSGi  *
    *                  applications.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: An EBA containing an EJB fails to       *
    *                      start. A WSVR0067E message indicates    *
    *                      NoClassDefFoundError caused by          *
    *                      NullPointerException.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an Eclipse Modelling Framework (EMF) package is
    initialized, it is registered with the package registry
    associated with the thread's context class loader. When the
    EJB Container is first used it attempts to read its
    configuration data from the package registry.  If the first
    application that uses the EJB Container is an OSGi application
    then the application startup will fail due to a failure while
    accessing the EJB Container's configuration stored in the
    package registry.
    The failure occurs because the context class loader set for
    the thread performing the start of the EJB Container for an
    OSGi application has been set to a classloader that is both
    different from, and not a parent of, the classloader that was
    used when the package was initially registered resulting in
    the EJB Container being unable to locate its required
    configuration.
    

Problem conclusion

  • The OSGi container was modifed so that the correct classloader
    was set as the thread's context class loader while starting the
    EJB Container during OSGi application startup.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.13 and 9.0.0.6.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Application startup order can be modified so that EJB
    Container initialization occurs during the startup of a
    non-OSGi application.
    

Comments

APAR Information

  • APAR number

    PI85587

  • 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

    2017-08-07

  • Closed date

    2017-09-18

  • Last modified date

    2017-09-18

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
17 June 2021