Intermittent JNDI exceptions when looking up data source in WebSphere Application Server 4.0 on Sun Solaris
 Technote (FAQ)
 
Problem
Using WebSphere® Application Server 4.0 (prior to Fix Pack 5) on Sun Solaris™ systems, the following exception might be issued intermittently when a JNDI™ lookup of a data source is done:

com.ibm.websphere.naming.CannotInstantiateObjectException: An unexpected
error occurred while attempting to deserialize retrieved object. Root
exception is java.lang.ClassCastException: Assigning instance of class
java.lang.String to field javax.naming.RefAddr#addrType
at
java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
at
java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
...
 
Cause
This is identified as a bug in the Sun JDK™. The bug ID is 4615373. It is documented here:
http://developer.java.sun.com/developer/bugParade/bugs/4615373.html
 
Solution
Upgrade to WebSphere Application Server 4.0.5 (or higher), which ships with a newer version of the Sun JDK within which the bug is fixed.

Alternatively, upgrade the Sun JDK to a version of 1.3.1_05 or later.

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): Solaris
Software version: 4.0.4
Software edition:
Reference #: 1116516
IBM Group: Software Group
Modified date: Sep 7, 2004