PQ54240: METHODS SET TO READ, THE EJBSTORE() STILL OCCURS

APAR status
Closed as program error.

Error description
For an entity bean, if I set the Access Intent of all the method
remote interface (RemoteInterface.*) to READ, I can indeed supre
ejbStore() at the end of the transaction.
However, if I set every single method on the RemoteInterface
individually to READ, the ejbStore() still occurs.
.
Customer was told this was a known problem and to open an apar
to the attention of Randy Schnier.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who       *
*                 specify the "*" wildcard to indicate that    *
*                 a given transactional, isolation level,      *
*                 or read-only attribute should apply to all   *
*                 methods within an EJB Home or Remote         *
*                 Interface.                                   *
*                                                              *
*                 Also users who wish to upgrade their EJB     *
*                 Container to the 4.0.2 level without         *
*                 applying the full 4.0.2 PTF.  The 4.0.2 EJB  *
*                 container includes a number of significant   *
*                 performance improvements vs. 4.0.1.          *
****************************************************************
* PROBLEM DESCRIPTION: Specifying * as wildcard for EJB        *
*                      method attributes not having desired    *
*                      effect                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When users specified "*" as an attribute on their EJB
Home or Remote interface to indicate that the attribute should
apply to all methods, the attribute was actually not applied
to all methods.
Problem conclusion
This e-fix corrects the problem for all attribute types on
EJB Home and Remote methods.

It is also a rollup of a collection of EJB container
functional and performance improvements that were made
between WebSphere 4.0.1 and 4.0.2.

IMPORTANT: This e-fix PQ54240 has a companion e-fix 
PQ57339
that must be applied either before or after PQ54240.  For
customer convenience, the 
PQ57339 e-fix is packaged in the
same e-fix download directory as PQ54240.
Temporary fix
Code update delivered to wasdoc0\APARS\PQ54240
Comments
APAR information
APAR number PQ54240
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-01
Closed date 2002-01-31
Last modified date 2002-01-31

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
CONTAINR          

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

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 #: PQ54240
IBM Group: Software Group
Modified date: Jan 31, 2002