Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
A NamingException indicating the Application Server could not resolve a URL may occur when looking up the JNDI name of an Enterprise Bean when Java Security is enabled: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is javax.naming.NamingException: Could not resolve URL: IOR: ... ... 0 at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:1232) 0 at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup( Helpers.java:925) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.processBoundObjectForLoo kup(CNContextImpl.java:2877) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CN ContextImpl.java:3974) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1876) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1777) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl. java:1434) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.jav a:616) ... Caused by: org.omg.CORBA.INTERNAL: vmcid: 0xc 9c25000 minor code: 7F3 completed: No 0 at com.ibm.ws390.orb.ORB.lookupLocalObject(ORB.java:1272) 0 at com.ibm.rmi.iiop.DataValueReader.newObjRef(DataValueReader.java: 937) 0 at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:563) 0 at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:528)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server for z/OS * **************************************************************** * PROBLEM DESCRIPTION: A CannotInstantiateObjectException * * occurred while the JNDI NamingManager * * was processing a * * javax.naming.Reference object. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Application Server may fail to lookup a JNDI name for an Enterprise Bean in the event the Naming manager throws a CannotInstantiateObjectException while processing a javax.naming.Reference object. Here is a snippet of the call stack that appears in the System log when exception occurs. com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is javax.naming.NamingException: Could not resolve URL: IOR: ... ... 0 at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:1232) 0 at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup( Helpers.java:925) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.processBoundObjectForLoo kup(CNContextImpl.java:2877) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CN ContextImpl.java:3974) 0 at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1876) ... Caused by: org.omg.CORBA.INTERNAL: vmcid: 0xc 9c25000 minor code: 7F3 completed: No 0 at com.ibm.ws390.orb.ORB.lookupLocalObject(ORB.java:1272) 0 at com.ibm.rmi.iiop.DataValueReader.newObjRef(DataValueReader.java: 937) 0 at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:563) 0 at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:528) ...
Problem conclusion
Apply APAR PI67629 to resolve the CannotInstantiateObjectException that occurred while the JNDI NamingManager was processing a javax.naming.Reference object. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.2. 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
PI67629
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-17
Closed date
2016-08-19
Last modified date
2016-08-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI71983
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022