PQ65352: JAVA EXCEPTION INADEQUATE FOR APPLICATION DEBUGGING IN A PRODUCTION ENVIRONMENT

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
One example:There is a java application that runs in a USS shell
The TestBean1 method then looks up TestBean2 via JNDI & invokes
 method on TestBean2. TestBean2 instantiates a regular java obj.
 called JavaClass and invokes a method on JavaClass. The method
 JavaClass throws an ArrayIndexOutOfBounds error. There is no
 catch inside JavaClass or TestBean2. The error is caught as a
 RemoteException in TestBean1.
The ArrayIndexOutOfBounds appears in the TRACEBUFFLOC defined
trace record output, but there is no data to help determine
where and why the ArrayIndexOutOfBounds exception occurred.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Bean method runtime exception           *
*                      information is not reported back to     *
*                      the client.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Bean method runtime exceptions are not saved and propagated
through the container when they occur. Instead of saving the
runtime exception, the container ultimately throws
TRANSACTION_ROLLBACK from post invoke (method postInvoke) and
nests the CSITransactionRolledbackException. The
CSITransactionRolledbackException should
not be nested and this is not helpful for debugging
the original source of the the problem.
Problem conclusion
Support has been modified such that instead of nesting the
CSITransactionRolledbackException exception, the original bean
method exception detail is passed to the TRANSACTION_ROLLBACK
when it is thrown from post invoke in EJSContainer, so the
original exception is nested in the exception stack trace.

APAR PQ65352 is associated with SERVICE LEVEL W401402 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ65352
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-16
Closed date 2002-10-10
Last modified date 2002-11-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ70733    UP02/10/16 P F210

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ65352
IBM Group: Software Group
Modified date: Nov 3, 2002