PM35068: LOOKUP OF STATEFUL EJB RETURNS PREVIOUSLY DESTROYED INSTANCE. LOOKUP, USE, THEN REMOVE AND LOOKUP GIVES DESTROYED INSTANCE.

Fixes are available

APAR status

Closed as program error.

Error description

A lookup is done from a servlet for a stateful EJB3.0, it is
used, then removee.  Then, when another lookup is performed,
you would we get the exact same instance of the destroyed EJB
that you had previously and when you try to use it you get the
following error:
3/16/11 9:15:36:667 EDT] 00000013 BusinessExcep E   CNTR0020E:
EJB threw an unexpected (non-declared) exception during
invocation of method "callStateful" on bean "BeanId
(RemoveEJBEar#RemoveEJB.jar#StatelessEjb, null)". Exception
data: javax.ejb.NoSuchEJBException:
Stateful bean BeanId(RemoveEJBEar#RemoveEJB.jar#StatefulEjb,
BECE9D9F-012E-4000-E000-18D40A00010E) was removed or timed out.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server version 7.0.                         *
****************************************************************
* PROBLEM DESCRIPTION: JNDI lookup of local stateful session   *
*                      bean returns previously destroyed       *
*                      instance.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
JNDI lookup of local stateful session bean returns previously
destroyed instance. Local stateful session beans are being
cached by the JNDI Context implementation. They should not be
cached because each lookup yields a new object instance.

Problem conclusion

The problem has been corrected and the beans are no longer
cached.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.19.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM35068
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-17
Closed date
2011-04-07
Last modified date
2011-04-07

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

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM35068: LOOKUP OF STATEFUL EJB RETURNS PREVIOUSLY DESTROYED INSTANCE. LOOKUP, USE, THEN REMOVE AND LOOKUP GIVES DESTROYED INSTANCE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?