PM13146: BBOO0221W: NMSV0605W: A JAVAX.NAMING.REFERENCE OBJECT, EXCEPTION. ASYNCHBEANS SERVICE NOT INITIALIZED

Fixes are available

APAR status

Closed as program error.

Error description

BBOO0221W: NMSV0605W: A javax.naming.Reference object,
Exception.   AsynchBeans Service not initialized
.
 When an Application has resources referenced in the EJB
Container to AsynchBeams and the Adjunct region is being started
the EJB container will perform a caching of handles as a
performance enhancement. Using the following method:
com.ibm.ejs.container.BeanMetaData.doConnectionHandlePerformance
Settings
 The following exception will be thrown as result of the
AsynchBeams Service not running on the Adjunct.
.
BBOO0221W: NMSV0605W: A javax.naming.Reference object looked up
from the context "xdcell/clusters/RTDS_IS_Cluster" with the name
"WorkManager" was sent to the JNDI Naming Manager and an
exception resulted. Reference data follows: Reference Factory
Class Name: com.ibm.ws.asynchbeans.naming.WorkManagerFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: com.ibm.websphere.asynchbeans.WorkManager
.
com.ibm.ws.asynchbeans.ServiceNotInitializedException:
AsynchBeans Service not initialized
at
com.ibm.ws.asynchbeans.J2EEServiceManager.getSelf(J2EEServiceMan
ager.java:217)
at
com.ibm.ws.asynchbeans.AsynchContextDescriptorImpl2.inflateConte
xt(AsynchContextDescriptorImpl2.java:163)
at
com.ibm.ws.asynchbeans.AsynchContextDescriptorImpl2.<init>(Async
hContextDescriptorImpl2.java:83)
at
com.ibm.ws.asynchbeans.AsynchBeanManager.<init>(AsynchBeanManage
r.java:142)
...

Local fix

```
NONE:
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1.0                               *
****************************************************************
* PROBLEM DESCRIPTION: Extraneous NMSV0605W warning messages   *
*                      appear in the log for the Adjunct       *
*                      when an application contains            *
*                      AsynchBean references.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The EJBContainer must run through some startup processing
on the Adjunct during application startup.  During this
startup an attempt is made to access all references for EJBs.
If an Asynchbean reference exists an NMSV0605W warning message
will appear in the logs because the Asynchbean service is not
started on the Adjunct.   Although this warning can be ignored
it should not occur.

Problem conclusion

The fix for this issue was to add a gate around the affected
EJBContainer code so that it will not execute on the Adjunct.
The code itself was for some handle performance tuning and
since the application never actually runs on the Adjunct it is
ok to skip this coded.

APAR PM13146 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.33 of WebSphere Application Server V6.1.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM13146
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-26
Closed date
2010-06-21
Last modified date
2010-10-02

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

PM23595

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R610 PSY UK59848
UP10/09/11 P F009

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM13146: BBOO0221W: NMSV0605W: A JAVAX.NAMING.REFERENCE OBJECT, EXCEPTION. ASYNCHBEANS SERVICE NOT INITIALIZED

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

R610 PSY UK59848

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

Share your feedback

Need support?