IBM Support

PM71107: APP FAILS TO START WITH CSCOPE AND @STARTUP EJB.

Fixes are available

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Application with EJB 3.1 module fails to start with the
following error.

Error:
Caused by: com.ibm.ejs.container.ContainerEJBException: Unable
to initialize deferred EJB.; nested exception is:
com.ibm.ejs.container.ContainerException: Failed to start
IBM_BPM_WEBPD_bpmdevinf029Node05_server1#PartialUpdate-ejb.jar#P
artialUpdateSchedulerStartupBean; nested exception is:
       com.ibm.ejs.container.EJBConfigurationException: Failed
to notify listeners - caught Throwable
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime$1.run(Abstrac
tEJBRuntime.java:2384)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime$1.run(Abstrac
tEJBRuntime.java:2314)
       at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.java:63)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.initializeDef
erredEJB(AbstractEJBRuntime.java:2313)
       at
com.ibm.ejs.container.HomeRecord.getHomeAndInitialize(HomeRecord
.java:405)
       at
com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:410)
       at
com.ibm.ejs.csi.EJBApplicationMetaData.createStartupBeans(EJBApp
licationMetaData.java:970)
       ... 17 more
Caused by: com.ibm.ejs.container.ContainerException: Failed to
start
IBM_BPM_WEBPD_bpmdevinf029Node05_server1#PartialUpdate-ejb.jar#P
artialUpdateSchedulerStartupBean; nested exception is:
       com.ibm.ejs.container.EJBConfigurationException: Failed
to notify listeners - caught Throwable
       at
com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:1
851)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.startBean(Abs
tractEJBRuntime.java:2594)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.initializeDef
erredEJBImpl(AbstractEJBRuntime.java:2461)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.access$300(Ab
stractEJBRuntime.java:210)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime$1$1.run(Abstr
actEJBRuntime.java:2347)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime$1$1.run(Abstr
actEJBRuntime.java:2341)
       at
com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
Impl.java:5413)
       at
com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM
anagerImpl.java:5539)
       at
com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityCon
text.java:255)
       at
com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime$1.run(Abstrac
tEJBRuntime.java:2340)
       ... 23 more
Caused by: com.ibm.ejs.container.EJBConfigurationException:
Failed to notify listeners - caught Throwable
       at
com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:1
715)
       ... 32 more
Caused by: com.ibm.ws.exception.RuntimeError:
java.lang.NullPointerException
       at
com.ibm.ws.cscope.CScopeMetaDataListener.metaDataCreated(CScopeM
etaDataListener.java:266)
       at
com.ibm.ws.runtime.component.MetaDataMgrImpl.fireMetaDataCreated
(MetaDataMgrImpl.java:279)
       at
com.ibm.ws.runtime.component.MetaDataMgrImpl.fireMetaDataCreated
(MetaDataMgrImpl.java:262)
       at
com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:1
709)
       ... 32 more
Caused by: java.lang.NullPointerException
       at
com.ibm.ws.cscope.CScopeMetaDataListener.metaDataCreated(CScopeM
etaDataListener.java:125)
       ... 35 more

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server versions V8.0.0 and V8.5.0 who make  *
*                  use of CScope and Startup beans             *
*                  (@Startup).                                 *
****************************************************************
* PROBLEM DESCRIPTION: Failed to notify listeners during use   *
*                      of CScope and Startup beans scenario.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During the startup of an application, the following
NullPointerException can occur:
Caused by: java.lang.NullPointerException
at
com.ibm.ws.cscope.CScopeMetaDataListener.metaDataCreated(CScopeM
etaDataListener.java:125)
This occurs because necessary MetaData used by CScope is not
yet available.  This has to due with the order in which
services are called and started when the application starts in
the case where @Startup is used.  That is, when @Startup is
used, the EJB Container processes this method during
application startup.  When CScope is used by the application,
this service is called during startup and it attempts to get
some meta data from another service.  However, the service
which it requests the data from has not yet been informed of
the application startup and as such has not yet had a chance to
create the meta data.  As such, null meta data is returned to
CScope which cases an NPE.

    



Problem conclusion


    

  • With this fix, code has been added to ensure the neccessary
meta data is available to CScope during the processing of a
startup bean.

The fix for this APAR is currently targeted for
inclusion in Service Levels (Fix Packs) 8.0.0.5 and 8.5.0.1 of
WebSphere Application Server versions 8.0.0 and 8.5.0.

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
    PM71107
    • 

  • Reported component name
    WEBSPHERE APP S
    • 

  • Reported component ID
    5724J0800
    • 

  • Reported release
    800
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2012-08-17
    • 

  • Closed date
    2012-10-02
    • 

  • Last modified date
    2012-10-02
    • 





    

  • 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


    

  • R800  PSY
       UP
    • 

  • R850  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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            29 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback