PQ59177: EJB.REMOVE() INCORRECTLY CALLED WHEN TWO CLIENTS ACCESS THE SAME INSTANCE OF STATEFUL SESSION EJB.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Two different clients access the same instance of stateful
session ejb at the same time from separate browsers. The
first one got the access, the second one failed on reentrant
exception, com.ibm.ejs.container.BeanNotReentrantException,
because the first client's remote method call was not yet
finished. The reentrant exception was expected and adheres
to the EJB spec.  The problem was the instance was removed,
ejb.remove() was called, after the second one failed to
access the bean instance. The instance no longer existed and
was not accessible to any client, including the first that
had a successful reference to it. This is not part of the
EJB spec and needs to be resolved.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: BeanNotReentrantException for stateful  *
*                      session bean leads to removal of the    *
*                      bean instance.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a client tries to access a stateful session bean and
a BeanNotReentrantException occurs, the bean instance is
destroyed.  Subsequent access to the bean instance results in
a NoSuchObjectException.
This is not consistent with the EJB 1.1 specification.  The
BeanNotReentrantException should be thrown, but the bean
instance should be left intact for future use by clients.
Problem conclusion
When a BeanNotReentrantException is detected the container no
longer removes the bean instance.

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

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF BBOZ0812 BBOZ0813      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ66020    UP02/05/17 P F205

  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 #: PQ59177
IBM Group: Software Group
Modified date: Jun 5, 2002