PQ94124: CLASSCASTEXCEPTION AFTER RECEIVING STALECONNECTIONEXCEPTION WHILE RUNNING EJB.

 Fixes are available

6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for AIX platforms
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
6.0.0.2: WebSphere Application Server Version 6.0.0 Fix Pack 2
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for HP-UX platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for OS/400 platforms
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Solaris platforms
6.0.0.3: WebSphere Application Server V6.0.0 Fix Pack 3
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Windows platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Linux platforms
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
6.0.1.2: WebSphere Application Server Version 6.0.1 Fix Pack 2
6.0.1: WebSphere Application Server Version 6.0 Refresh Pack 1



APAR status
Closed as program error.

Error description
In order to handle stale connections in a local stateless
session bean
we adopt the following strategy:
  Catch the com.ibm.websphere.ce.cm.StaleConnectionException
  Invalidate the transaction using
getSessionContext().setRollbackOnly()
  Rethrow a user defined exception.
  The class which accesses the stateless session bean`s method
catches
refreshes the connection after it fails.  I should point out
that we
use a single physical connection to support our application.
.
In our production environment, we use Oracle 8i.
.
This strategy worked when we used WebSphere 5.0, but fails with
WebSphere 5.1.0.3.  In WebSphere 5.1.0.3 a ClassCastException is
registered.
Local fix
No local fix.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server application     *
*                 developers of Enterprise Java Beans (EJBs).  *
****************************************************************
* PROBLEM DESCRIPTION: ClassCastException is thrown when an    *
*                      application logic is trying to          *
*                      recover from StaleConnectionException.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An application may have logic to recover from
com.ibm.websphere.ce.cm.StaleConnectionException and throw an
application exception. The client, instead of receiving
application exception, gets ClassCastException incorrectly.
Problem conclusion
Modified logic to correctly handle such a case and avoid
throwing of ClassCastException.
Temporary fix Comments
APAR information
APAR number PQ94124
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-09-13
Closed date 2004-11-05
Last modified date 2005-01-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBCNTR          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PQ94124
IBM Group: Software Group
Modified date: Jan 27, 2005