PQ73181: Do not remove EJBException from the Chained exception

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
EJBException, if thrown the EJB is not being reported back to
the client
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server J2EE clients    *
*                 who have a dependency on chained exception   *
****************************************************************
* PROBLEM DESCRIPTION: A chained EJBException for a remote     *
*                      client is missing                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the EJB chained an EJBException, the J2EE client would not
see the EJBException chained to the RemoteException.
Problem conclusion
This fix ensures consistency of chained exception as compared to
5.0 release.
Temporary fix Comments
APAR information
APAR number PQ73181
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-04-14
Closed date 2003-04-29
Last modified date 2003-04-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBContr          

Publications Referenced

Fix information

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 #: PQ73181
IBM Group: Software Group
Modified date: Apr 29, 2003