EJB Container; 4.0.2-4.0.7: Component Cumulative fix
for EJB Container
Downloadable files
Abstract
EJB Container component cumulative fix for WebSphere®
Application Server V4.0.2 through V4.0.7.
Download Description
EJB Container Component Cumulative; 4.0.2-4.0.7: Resolves the
following problems:
BeanOActivationFailureException occurs after migration from 4.0.3
(PQ84963)
Custom Finder enhancements supporting dynamic SQL "FOR UPDATE"
enhancements (PQ74423)
LRUCache object discarded without executing castout policy, memory
leak (PQ72451)
No exception return to client when transaction times out (PQ71200)
Bean remove corrupts DB primary key field for tables using foreign key
(PQ68515)
Better logging and performance for stateless session beans (PMR
56147,487)
Create copy of the primary key object when NoLocalCopies used
(PQ62081)
Correctly support persistence operations when PQ57073 (CM DB2 390
support not applied) (PQ60468)
Synchronize entity bean to database prior to ejbFind (PMR 07668, 419,
000)
Pass-by-value class enhancements for WebSphere 390 interoperability
(PQ57731)
Bean not re-entrant exception occurs with transaction in ejbcreate()
method call (PQ56091)
Diagnostic/service tracing enhancements (General)
General problems corrected prior to customer report:
If a CMP bean a, has a method b, and a.b() contains a call to bean b,
method b, e.g. b.b(), and b.b() received an unchecked or system exception,
bean b is discarded correctly, but bean a is not. Consequently, bean a is
placed back into the reuse pool, but is the destroyed state, and useable.
If tracing has been enabled, the following will appear in the log:
InvalidBeanOStateException(current = DESTROYED, expected = POOLED)
If method-level attributes are specified in the bean's deployment
descriptor for transactions, isolation level, or read-only, and the
attribute is specified to apply to a specific method with a specific
signature, and one or more of the arguments in the signature is an array
type, the container does not correctly apply the attribute to the
corresponding method on the EJB.
On some platforms, a problem has been found where a call to the
reflection API getField(name) results in a NoSuchFieldException even
though the field does exist. This may be an intermittent problem which
will be seen when installing an application with an Entity Bean with
Container Managed Persistence fields.
This fix provides a workaround for this problem, by merely attempting the
call a second time. This is a temporary fix until a permanent solution can
be obtained for the Java™ SDK
Overloaded EJBObject methods, such as remove, did not get the correct
Transaction Attributes applied. This has been fixed.
Allows EJB access from beforeCompletion on SessionSynch enabled
Session Beans, and from ejbStore on EntityBeans.