Fixes are available
PI63532:JNDI Lookup Failures
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
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
This APAR fixes several problems relating to JNDI lookups.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes several problems * * relating to JNDI lookups in Application * * Client Modules. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes several problems relating to JNDI lookups in Application Client Modules. * A null pointer exception occurring when processing a javax.naming.Reference object: Caused by: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NullPointerException] at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:1228) at com.ibm.ws.naming.java.javaCNRootContextImpl.processBoundObjectF orLookup(javaCNRootContextImpl.java:610) at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CN ContextImpl.java:3974) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1876) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1777) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl. java:1434) at com.ibm.ws.naming.java.javaCNRootContextImpl.lookupExt(javaCNRoo tContextImpl.java:368) at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLConte xtRoot.java:468) at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextR oot.java:370) at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.jav a:161) at javax.naming.InitialContext.lookup(InitialContext.java:428) at com.sun.ts.tests.ejb30.common.helper.ServiceLocator.lookup(Servi ceLocator.java:72) at com.sun.ts.tests.ejb30.common.helper.ServiceLocator.lookupNoTry( ServiceLocator.java:28) ... 41 more Caused by: java.lang.NullPointerException at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObject Instance(ConnectionFactoryBuilderServerImpl.java:1198) at com.ibm.ejs.j2c.ServerFunction.processObjectInstance(ServerFunct ion.java:2006) at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(C onnectionFactoryBuilderImpl.java:662) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstanceUsing ObjectFactoryBuilders(ObjectFactoryHelper.java:349) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance(Obje ctFactoryHelper.java:89) at org.apache.aries.jndi.OSGiObjectFactoryBuilder.getObjectInstance (OSGiObjectFactoryBuilder.java:62) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.j ava:311) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:1118) ... 53 more * A lookup faiure occuring as a NameNotFoundException. For example: [javatest.batch] Caused by: javax.naming.NameNotFoundException: Name "AppClientMyTestConnectionFactory" not found in context "java:global". [javatest.batch] at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java :1229) [javatest.batch] at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1142) [javatest.batch] at com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImp l.java:1436) [javatest.batch] at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLConte xtImpl.java:48 0) [javatest.batch] at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLConte xtRoot.java:48 5) [javatest.batch] at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLConte xtRoot.java:46 8) [javatest.batch] at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextR oot.java:370) [javatest.batch] at javax.naming.InitialContext.lookup(InitialContext.java:428) [javatest.batch] at com.sun.ts.lib.util.TSNamingContext.lookup(TSNamingContext.java: 62) [javatest.batch] at com.sun.ts.tests.jms.ee20.resourcedefs.annotations.Client.doLook upJMSObjects(Client.java:223) [javatest.batch] ... 43 more
Problem conclusion
The problems were fixed by code updates in several areas. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.1. 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
PI63532
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-06
Closed date
2016-06-23
Last modified date
2016-06-23
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
R900 PSY
UP
Document Information
Modified date:
04 May 2022