PQ70093: CUSTOMER RESTARTS THEIR ACCESS BEAN APPLICATION AND NOT THE APP SERVER THEY GET CLASS CAST EXCEPTION.

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
In 5.0 WSAD test environment, customer restarts an EJB access be
an application and gets a Class Cast Exception. They make no
changes to the .ear. If they restart the application server they
do not get the class cast exception.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 WebSphere Studio Application Developer       *
*                 Version 5.0 in the Unit Test Environment     *
****************************************************************
* PROBLEM DESCRIPTION: In 5.0 WSAD test environment, customer  *
*                      restarts an EJB access bean             *
*                      application and gets a Class Cast       *
*                      Exception. They make no changes to the  *
*                      .ear. If they restart the application   *
*                      server they do not get the class cast   *
*                      exception.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem was one of caching of the home interface within
the Access bean by the initial context was causing ClassCast
Exception.  We globally cache the InitialContext based on
the properties used.  If the properties change, we will
change the cached value.  In this scenario (application
restarting due to a change to the bean class), the cached
home interface was removed from the global cache but the
old InitialContext was used.  In the WebSphere implementation,
this context held the old cached home, thus the cause of the
ClassCastException.
Problem conclusion
This fix will now cache the current context ClassLoader when the
InitialContext is created and cached.  If the ClassLoader is
different the next time the context is retrieved (on application
restart), a new InitialContext will be created.
Temporary fix Comments
APAR information
APAR number PQ70093
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-01-21
Closed date 2003-02-13
Last modified date 2003-09-15

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ70093
IBM Group: Software Group
Modified date: Sep 15, 2003