PM62057: UPDATING OR RESTARTING SCA APPLICATION CAUSES CORBA.OBJECT_NOT_EXIST ERROR ON INVOKE

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
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

APAR status

• Closed as program error.

Error description

• Updating or restarting SCA application causes
  CORBA.OBJECT_NOT_EXIST error on invoke
  
  [1/24/12 10:50:52:126 EST]     FFDC
  Exception:org.omg.CORBA.OBJECT_NOT_EXIST
  SourceId:com.ibm.ws.sca.internal.binding.handler.SCAImportBindin
  gHandler
  ProbeId:002
  Reporter:com.ibm.ws.sca.internal.binding.handler.SCAImportBindin
  gHandler
  @6ff66ff6
  org.omg.CORBA.OBJECT_NOT_EXIST: SERVANT_NOT_FOUND (4) for key
  
  minor code: C14  completed: No
   at
  com.ibm.rmi.corba.ObjectManager.lookupServant(ObjectManager.java
  :110)
   at
  com.ibm.CORBA.iiop.ServerDelegate.getServant(ServerDelegate.java
  :312)
   at
  com.ibm.CORBA.iiop.ClientDelegate.lookupServant(ClientDelegate.j
  ava:635)
   at
  com.ibm.CORBA.iiop.ClientDelegate.is_local(ClientDelegate.java:5
  72)
   at
  org.omg.CORBA.portable.ObjectImpl._is_local(ObjectImpl.java:381)
   at
  com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler.
  processClassicMessage(SCAImportBindingHandler.java:1012)
  

Local fix

• Restart environment
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Updating or restarting a Service        *
  *                      Component Architecture (SCA)            *
  *                      application causes a                    *
  *                      CORBA.OBJECT_NOT_EXIST error on invoke  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Process Server caches EJB stubs that point to
  modules registered by the SCA runtime. These registered names
  can change when the application is restarted because a list of
  services queried by the SCA runtime and used to construct the
  module name does not have a pre-determined order. Therefore
  the WebSphere Process Server stubs can fall out of sync with
  the SCA runtime and no longer find these services.
  

Problem conclusion

• The SCA runtime no longer includes the specific service name
  as part of the registered module name. It cannot change
  between application restarts and will not fall out of sync
  with the WebSphere Process Server stubs.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.4.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  The Feature Pack for SCA fix for this APAR will be delivered
  via APAR PM57831.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM57831

• 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