PQ73181: Do not remove EJBException from the Chained exception | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description EJBException, if thrown the EJB is not being reported back to the clientLocal 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 is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
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
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.