IBM Support

PI87723: NULLPOINTEREXCEPTION OCCURS DURING APPLICATION START

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A NullPointerException is seen in the SystemOut.log log file
    after application start.  The failure does not appear to
    affect any function of the application.
    
    Example error.
    
    [9/21/17 10:44:15:089 CEST] 00000091 annotations   E   Merge
    Processing
    Failure
    java.lang.NullPointerException
    at
    com.ibm.ws.amm.merge.common.data.SessionBeanData.isNoInterfaceVi
    ew(Sessi
    onBeanData.java:724)
    at
    com.ibm.ws.amm.merge.common.data.SessionBeanData.getSessionBusin
    essMetho
    ds(SessionBeanData.java:541)
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.getSess
    ionBeanB
    usinessMethods(TransactionAttributeMergeAction.java:1399)
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.getBusi
    nessMeth
    ods(TransactionAttributeMergeAction.java:1380)
    at
    com.ibm.ws.amm.merge.ejb.TransactionAttributeMergeAction.merge(T
    ransacti
    onAttributeMergeAction.java:657)
    at
    com.ibm.ws.amm.AnnotativeMetadataManagerImpl.performMergeOperati
    ons(Anno
    tativeMetadataManagerImpl.java:572)
    at
    com.ibm.ws.amm.AnnotativeMetadataManagerImpl.merge(AnnotativeMet
    adataMan
    agerImpl.java:440)
    at
    com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(Anno
    tationsP
    rocessorImpl.java:175)
    at
    com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(Anno
    tationsP
    rocessorImpl.java:77)
    at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EJBJarFileI
    mpl.proc
    essAnnotations(EJBJarFileImpl.java:584)
    at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EJBJarFileI
    mpl.getD
    eploymentDescriptor(EJBJarFileImpl.java:475)
    at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EJBJarFileI
    mpl.getD
    eploymentDescriptor(EJBJarFileImpl.java:253)
    at
    com.ibm.etools.commonarchive.impl.EJBJarFileImpl.getBindings(EJB
    JarFileI
    mpl.java:758)
    at
    com.ibm.ws.ejbcontainer.facade.deploy.DeployedEJBModule.getBindi
    ng(Deplo
    yedEJBModule.java:788)
    at
    com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJB
    Containe
    rImpl.java:3258)
    at
    com.ibm.ws.ejbcontainer.facade.EJBFacadeManagerImpl.startEJBModu
    le(EJBFa
    cadeManagerImpl.java:189)
    at
    com.ibm.ws.container.binding.ejb.ImmediateEJBRegistrationManager
    .add(Imm
    ediateEJBRegistrationManager.java:38)
    at
    com.ibm.ws.container.binding.ejb.StatelessSessionBeanBindingMana
    gerImpl.
    add(StatelessSessionBeanBindingManagerImpl.java:164)
    at
    com.ibm.ws.container.binding.classicsca.ejb.EJBDefaultBindingMan
    agerImpl
    .add(EJBDefaultBindingManagerImpl.java:331)
    at
    com.ibm.ws.sca.internal.binding.handler.NativeSCAExportModuleLis
    tener.ac
    tivateSCAEndpoints(NativeSCAExportModuleListener.java:210)
    at
    com.ibm.ws.sca.internal.binding.handler.NativeSCAExportModuleLis
    tener.on
    Started(NativeSCAExportModuleListener.java:116)
    at
    com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.initC
    ontentEx
    tensionOnStarted(MessageDispatcherImpl.java:2238)
    at
    com.ibm.ws.sca.internal.container.impl.ContainerImpl.startModule
    Componen
    ts(ContainerImpl.java:1161)
    at
    com.ibm.ws.sca.internal.container.impl.ContainerImpl.triggerModu
    leCompon
    ent(ContainerImpl.java:1126)
    at
    com.ibm.ws.sca.internal.managed.ManagedServerComponentImpl.appli
    cationSt
    ateChanged(ManagedServerComponentImpl.java:742)
    at
    com.ibm.ws.sca.internal.managed.ManagedServerComponentImpl.state
    Changed(
    ManagedServerComponentImpl.java:664)
    

Local fix

  • Processing continues, startup completes with no loss of
    function.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NullPointerException occurs when an   *
    *                      EJB is defined without specifying an    *
    *                      EJB class.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    IBM Business Process Manager (BPM) uses a WebSphere
    Application Server interface that dynamically creates an EJB
    during application start.  The code that creates the EJB
    failed to specify a class for the EJB.  The WebSphere
    Application Server code that merges EJB annotations and the
    ejb-jar.xml deployment descriptor failed to catch this problem
    and attempted to use the EJB class.  This resulted in a
    NullPointerException.
    The result of the exception is that the EJB merge processing
    did not complete for the EJB in question, which means that the
    generated ejb-jar_merged.xml had incomplete information for
    this EJB. This had no effect on the application in this case,
    since the EJB runtime code does not use the ejb-jar_merged.xml
    file.
    After the application starts, the following exception is found
    in the SystemOut.log:
    [9/21/17 10:44:15:089 CEST] 00000091 annotations   E   Merge
    Processing Failure java.lang.NullPointerException at
    com.ibm.ws.amm.merge.common.data.SessionBeanData.isNoInterfaceVi
    ew(SessionBeanData.java:724)
    

Problem conclusion

  • Two updates were made for this APAR. First the code that
    dynamically creates an EJB during application start was
    updated to include an EJB class.  This change was only
    needed in V8.5.5 as V9.0 already includes the EJB class.
    
    The second update was in the code that merges the annotation
    and descriptor data for EJBs.  It will now catch the problem,
    if it occurs, and display a warning message rather than a
    NullPointerException. This part is changed in V8.5.5 and V9.0.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.7.  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

    PI87723

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-21

  • Closed date

    2017-11-27

  • Last modified date

    2017-11-27

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

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

Document Information

Modified date:
18 October 2021