Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Application fails at server startup with the following error: Error Bootstrapping see console for details : java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST 0xc9c213e1 No; nested exception is: org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: 0xc9c21000 minor code: 3E1 completed: No at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDeleg ateImpl.java:279) at javax.rmi.CORBA.Util.mapSystemException(Util.java:84) ....... skipping application specific code ...... Caused by: org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: 0xc9c21000 minor code: 3E1 completed: No at com.ibm.ws390.orb.ClientDelegate.commonInvoke(ClientDelegate.jav a:1324) at com.ibm.ws390.orb.ClientDelegate.invoke(ClientDelegate.java:888) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:484) at canada.borderservices.common.environment.ejb._PropertyProviderHo me_Stub.create(_PropertyProviderHome_Stub.java:215) ... 66 more Caused by: org.omg.CORBA.INTERNAL: vmcid: 0xc9c21000 minor code: 3E1 completed: No at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1345) at com.ibm.rmi.util.Utility.readSystemException(Utility.java:1920) at com.ibm.rmi.iiop.CDRReader.readSystemException(CDRReader.java:10 42) at com.ibm.ws390.orb.ClientDelegate.commonInvoke(ClientDelegate.jav a:1259) WAS is starting the application and loading EJB metadata, and as a result of this, loads one of their application classes. That class contains a static initializer that is calling down to some other code which ends up invoking "create" on an object. However, since we're on a thread that is starting an application we have an optimization flag set called "EJB lazy activation" which means we don't actually activate EJBs since we are just starting the app (we'll activate them later after the app is started, when they are invoked). This is only meant to apply to the application that is starting.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Application fails at server startup * * with the following error: * * Error Bootstrapping see console for * * details : * * java.rmi.NoSuchObjectException: * * CORBA OBJECT_NOT_EXIST * * 0xc9c213e1 No; nested exception is: * * org.omg.CORBA.OBJECT_NOT_EXIST: * * vmcid: 0xc9c21000 minor * * code: 3E1 completed: No * **************************************************************** * RECOMMENDATION: * **************************************************************** The default behavior when starting an application is not to activate EJBs in that application. However, a problem exists that prevents any EJB home objects from being looked up by a thread that is currently starting an application, even if the home object belongs to another application. This can create a problem if code, such as a static initializer, runs at application startup and attempts to lookup an EJB home in another application. In such a case, the lookup will fail with the following exception: org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: 0xc9c21000 minor code: 3E1 completed: No at com.ibm.ws390.orb.ClientDelegate.commonInvoke(ClientDelegate.jav a:1324) at com.ibm.ws390.orb.ClientDelegate.invoke(ClientDelegate.java:888) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:484)
Problem conclusion
Obsolete code has been eliminated. APAR PM54828 is currently targeted for inclusion in WebSphere Application Server V7.0 Fix Pack 7.0.0.25. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM54828
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-21
Closed date
2012-03-14
Last modified date
2012-11-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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK81738
UP12/10/04 P F210
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 October 2021