PQ51386: JAVA.LANG.NOCLASSDEFFOUNDERROR FROM JNDI LOOKUP

APAR status
Closed as program error.

Error description
When executing a JNDI lookup of an object bound as a
javax.naming.Referenceable, javax.naming.Reference, or
java.io.Serializable, processing fails because a class
required to instantiate the object being looked up cannot
be found.
Defect 110542
Local fix Problem summary
The naming code is not using the context classloader to
deserialize objects .  This will result
in ClassNotFoundExceptions if the class is not present in
the bootstrap classloader.
The following error was reported by WebSphere Business
Components team:
NMSV0610I: A NamingException is being thrown from a
javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ejs.ns.jndi.CNContextImpl
Context method: lookup
Context name: domainRoots/UnspecifiedDomainName/legacyRoot
Target name:
BCServices/ApplicationContext/com.ibm.wsbc.bcs_DefaultUser
Other data:
Exception stack trace:
com.ibm.websphere.naming.CannotInstantiateObjectException:
ClassNotFoundException occurred while attempting to
deserialize retrieved object.  Root exception is
java.lang.ClassNotFoundException:
com.ibm.wsbc.bcs.MapWrapper
Without this fix, all the "common" jar files (e.g.
BCServicesCommon.jar) must either be explicitly
specified in the JVM classpath or added to the WebSphere
lib/ext directory.  Adding them to the
classpath becomes a problem for OrderCapture because there
are so many and we have run into classpath
length limitations.  Adding them to the WebSphere lib/ext
directory is undersireable because that is
not intended for application code and does not allow for
different versions of jar files on the same
server.
This fix allows the "common" jar files to be added to the
OrderCapture ear file and thus reside in the
same directory as the deployed jar files.
Problem conclusion
into the 4.0.2 ptf.
Temporary fix Comments
APAR information
APAR number PQ51386
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-08-10
Closed date 2001-08-23
Last modified date 2001-08-23

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
NAMING          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ51386
IBM Group: Software Group
Modified date: Aug 23, 2001