PQ61224: CUSTOMER IS GETTING NULL POINTER EXCEPTION FROM THE EJB CONTAINER WHEN HE SHOULD HAVE BEEN GETTING AN SQL EXCEPTION.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
PROBLEM:  Customer is getting NULL POINTER EXCEPTION from the
EJB container when he should have been getting an SQL EXCEPTION.
The particular SQL EXCEPTION that is being thrown is not
expected by the container and therefore the container fails with
a NULL pointer exception.  The client would therefore see this
NULL pointer exception instead of the root cause, the SQL
exception.
.
PTF: EJB Container now handles all types of SQL exceptions. The
original SQL exception will be thrown instead of a NULL pointer
exception begin thrown from the EJB Container.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: The WebSphere EJB Container throws      *
*                      NullPointerException when an SQL        *
*                      exception should be reported for a CMP  *
*                      bean create failure.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a CMP bean create fails due to an SQL error, the container
sometimes throws a NullPointerException instead of the original
SQL exception.  The container monitors for certain SQL States
such as duplicate key errors.  However, in this case, an SQL
exception is thrown that had a NULL SQL State. The container
was not expecting this and tried to execute an equals method on
the SQLState therefore hitting a NullPointerException.
Problem conclusion
The WebSphere EJB container no longer assumes that all SQL
exceptions will have non-NULL SQL States.

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

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ66835

Modules/Macros
BBOUBINF BBOZ0812 BBOZ0813      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ66835    UP02/06/06 P F206

  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 #: PQ61224
IBM Group: Software Group
Modified date: Jul 3, 2002