Fixes are available
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Clients, non-EJB3.0-compliant Servers, or stack products that invoke methods on EJB3.0-compliant servers may receive exception classes in return that are new to EJB 3.0 and therefore may cause problems.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: Clients that are not EJB 3.0 * * compliant receive EJB 3.0 specific * * exceptions, causing unexpected * * behavior. * **************************************************************** * RECOMMENDATION: * **************************************************************** Unexpected results can occur if a non-EJB 3.0 compliant server or client receives an EJB 3.0 specific exception from an EJB 3.0 compliant server. This will occur because the client does not have the new EJB 3.0 exception classes in it's classpath.
Problem conclusion
This APAR fixes this problem by providing the new EJB 3.0 specific exception classes in a new ejb3exceptions.jar file that is contained within the <WAS-HOME>/runtimes directory of the EJB 3.0 compliant server. This JAR file can then be copied, by the user, into the <WAS-HOME>/lib directory of the clients and servers that are not EJB 3.0 compliant. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23 for the Feature Pack for EJB 3.0 and also fixpack 7.0.0.3 for WebSphere Application Server. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK78404
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-09
Closed date
2009-01-23
Last modified date
2009-01-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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
29 December 2021