PQ58443: WHEN INSTALLING AN EAR WITH EJB'S IN WAS 4.0.2 AND CHOOSING REGENERATE THE DEPLOYED CODE, THERE ARE PERFORMANCE ISSUES

 A fix is available

EJB Container; 4.0.2-4.0.7: Component Cumulative fix for EJB Container



APAR status
Closed as program error.

Error description
This apar is to report the failure of the fix for apar 
pq57446.
The fix originaly provided creates DuplicateKeyException.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Entity Beans.                                *
****************************************************************
* PROBLEM DESCRIPTION: The following exception may be logged:  *
*                      java.lang.IllegalStateException         *
*                      when a transaction is rolled back.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The user may see the following exception logged:
   java.lang.IllegalStateException
   at com.ibm.ejs.container.EntityBeanO.passivate
                                         (EntityBeanO.java:642)
when a transaction is rolled back.  This actually occurs
during rollback processing, but may appear to occur prior to
the rollback, as it is logged before the rollback is logged.

And/or the user may experience various problems that would
result from object inheritance nor working correctly, such as
objects being returned as instances of a parent class from
finder methods.

The may result in abnormal application behavior if the
subclass that should have been returned overrode methods of
the parent.  In this case, the parent method would be invoked
instead of the subclass override.

This may also result in data corruption, as the Entity may
be stored to the database as the parent class, which would
change the discriminator to indicate the database row was of
the parent type, and may also null out any columns which are
exclusively for subclass use.
Problem conclusion
Code in the WebSphere EJB Container component was not properly
checking the 'discriminator' column in the database to determine
the correct class of Entity Bean to return for some finder
methods.

A code change has been made in the EJB Container component to
correct this, and the customer should apply efix
PQ58443_eFix.jar to resolve the problem.
Temporary fix
PQ58443_eFix.jar
Comments
APAR information
APAR number PQ58443
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-02-26
Closed date 2002-03-29
Last modified date 2002-03-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBCONTR          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58443
IBM Group: Software Group
Modified date: Mar 29, 2002