PK71873: NAMENOTFOUNDEXCEPTION OCCURS FOR JAVA:COMP WHEN LOOKUP PERFORMED IN EJB PREDESTROY CALLBACK (LIKE EJBREMOTE).

Fixes are available

APAR status

Closed as program error.

Error description

When the WebSphere Application Server removes a stateless or
message-driven enterprise bean the PreDestroy callback method
(like ejbRemote) is called, and may fail if it performs a
lookup in java:comp. The failure will be similar to the
following:

NMSV0310E: A JNDI operation on a "java:" name cannot be
completed because the server runtime is not able to
associate the operation's thread with any J2EE application
component.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM? WebSphere?                *
*                  Application Server V7.0.0                   *
****************************************************************
* PROBLEM DESCRIPTION: A NameNotFoundException may occur       *
*                      when performing a lookup in the         *
*                      PreDestroy method of a stateless or     *
*                      message-driven bean.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The enterprise beans container is not providing access to the
environment naming context (java:comp/env JNDI context) for
the PreDestroy method of stateless session and message-driven
beans.  If the code in a PreDestroy method attempts to perform
a lookup in the java:comp/env JNDI context, the lookup will
fail with a NameNotFoundException.

Note that an application has no control over when a bean is
removed or when PreDestroy is called, so it is unlikely this
failure has an immediate impact on the function of the
application.  The only symptom of the problem will be a
message in the system out log and FFDC log entries.

Problem conclusion

The application server enterprise beans Container will be
changed to provide access to the environment naming context
(java:comp/env JNDI context) during PreDestory for stateless
and message-driven beans.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK71873
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
2008-09-10
Closed date
2008-10-29
Last modified date
2008-10-29

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":"BU053","label":"Cloud & Data Platform"},"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:
23 October 2021

Tips

PK71873: NAMENOTFOUNDEXCEPTION OCCURS FOR JAVA:COMP WHEN LOOKUP PERFORMED IN EJB PREDESTROY CALLBACK (LIKE EJBREMOTE).

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?