PM82578: NON-EJB RMI CALLS FAIL WITH NULLPOINTEREXCEPTION WHEN SERVER IS CONFIGURED TO START COMPONENTS AS NEEDED

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

APAR status

• Closed as program error.

Error description

• The following NullpointerExceptions can be seen in the JVM
  SystemOut.log and FFDC files while starting the server.
  
  Caused by: java.lang.NullPointerException
  at
  com.ibm.ejs.container.EJSContainer.popORBDispatchClassLoader(EJS
  Container.java:5716)
  at
  com.ibm.ejs.container.EJSContainer.postInvokeORBDispatch(EJSCont
  ainer.java:5702)
  at
  com.ibm.ejs.oa.EJSRootOAImpl.postinvoke(EJSRootOAImpl.java:335)
  at
  com.ibm.rmi.corba.ObjectManager.postinvoke(ObjectManager.java:19
  3)
  at
  com.ibm.CORBA.iiop.ServerDelegate.doPostinvoke(ServerDelegate.ja
  va:1042)
  at
  com.ibm.CORBA.iiop.ClientDelegate.returnLocalServant(ClientDeleg
  ate.java:1149)
  at
  com.ibm.CORBA.iiop.ClientDelegate.servant_postinvoke(ClientDeleg
  ate.java:890)
  at
  com.ibm.CORBA.iiop.ClientDelegate.servant_preinvoke(ClientDelega
  te.java:822)
  at
  org.omg.CORBA.portable.ObjectImpl._servant_preinvoke(ObjectImpl.
  java:418)
  
  java.lang.NullPointerException
  at
  com.ibm.ejs.container.EJSDeployedSupport.<init>(EJSDeployedSuppo
  rt.java:415)
  at
  com.ibm.ejs.container.EJSDeployedSupportStack.<init>(EJSDeployed
  SupportStack.java:96)
  at
  com.ibm.ejs.container.EJBThreadData.<init>(EJBThreadData.java:11
  9)
  at
  com.ibm.ejs.container.EJSContainer$1.initialValue(EJSContainer.j
  ava:712)
  at
  com.ibm.ejs.container.EJSContainer$1.initialValue(EJSContainer.j
  ava:708)
  at com.ibm.ws.util.WSThreadLocal.get(WSThreadLocal.java:85)
  at
  com.ibm.ejs.container.EJSContainer.preInvokeORBDispatch(EJSConta
  iner.java:5648)
  at
  com.ibm.ejs.oa.EJSRootOAImpl.preinvoke(EJSRootOAImpl.java:322)
  at
  com.ibm.rmi.corba.ObjectManager.preinvoke(ObjectManager.java:206
  )
  at
  com.ibm.CORBA.iiop.ServerDelegate.doPreinvoke(ServerDelegate.jav
  a:1032)
  at
  com.ibm.CORBA.iiop.ClientDelegate.getLocalServant(ClientDelegate
  .java:1132)
  at
  com.ibm.CORBA.iiop.ClientDelegate.servant_preinvoke(ClientDelega
  te.java:749)
  at
  org.omg.CORBA.portable.ObjectImpl._servant_preinvoke(ObjectImpl.
  java:418)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.0       *
  *                  users of Enterprise Java Beans (EJB) and    *
  *                  the "start components as needed" server     *
  *                  configuration option                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: An application can fail to start.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the EJB container starts, it registers as a collaborator
  with the ORB and then finishes starting.  If the ORB calls the
  collaborator before the EJB container has fully started, a
  NullPointerException occurs.
  Normally, this will not occur because all server components,
  including the EJB container, are started serially before any
  application is started.  When the "start components as needed"
  server option is enabled, the EJB container can be started in
  parallel with other components, which means it can register a
  collaborator with the ORB before it has fully started.
  

Problem conclusion

• The EJB container is changed to fully start prior to
  registering as a collaborator with the ORB.  Additionally, the
  specific failing code path has been updated to be robust even
  if the EJB container is not started (for example, in case the
  EJB container has been stopped).
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.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 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

• R800 PSY

     UP