PK87672: METADATANOTAVAILABLEEXCEPTION WHEN RESGISTERING A PROFILE TO THE ADMINISTRATIVE AGENT.

Fixes are available

APAR status

Closed as program error.

Error description

When registering a profile with the administrative agent, a
com.ibm.websphere.management.exception.
MetadatNotAvailableException: Could not obtain managed object
metadata from Config Repository is seen in the process log.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server        *
*                  version 7.0 users.                          *
****************************************************************
* PROBLEM DESCRIPTION: MetadataNotAvailableException when      *
*                      registering to the administrative       *
*                      agent.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When registering an application server to the administrative
subsystem, the following FFDC event may be seen in the JVM log
when the status cache code attempts to determine if an
application server is a DMZ Secure Proxy Server for IBM
WebSphere Application Server:
FFDC Exception:com.ibm.websphere.management.exception.MetadataNo
tAvailableException SourceId:com.ibm.ws.management.status.NodeAg
entStatusCache.createStatusCacheExtensionClassList ProbeId:128
Reporter:com.ibm.ws.management.status.NodeAgentStatusCache
com.ibm.websphere.management.exception.MetadataNotAvailableExcep
tion: Could not obtain managed object metadata from Config Repos
itory.
  at com.ibm.ws.management.metadata.ManagedObjectMetadataAccesso
rImpl.extractMetadata(ManagedObjectMetadataAccessorImpl.java:281
  at com.ibm.ws.management.metadata.ManagedObjectMetadataAccesso
rImpl.getMetadataProperties(ManagedObjectMetadataAccessorImpl.ja
va:174)
  at com.ibm.websphere.management.metadata.ManagedObjectMetadata
Helper.getNodeBaseProductShortName(ManagedObjectMetadataHelper.j
ava:565)
  at com.ibm.ws.management.status.NodeAgentStatusCache.createSta
tusCacheExtensionClassList(NodeAgentStatusCache.java:158)
  at com.ibm.ws.management.status.NodeAgentStatusCache.createSta
tusCacheExtensions(NodeAgentStatusCache.java:114)
  at com.ibm.ws.management.status.AbstractStatusCache.<init>(Abs
tractStatusCache.java:291)
  at com.ibm.ws.management.status.NodeAgentStatusCache.<init>(No
deAgentStatusCache.java:100)
  at com.ibm.ws.management.status.StatusCacheFactory.getStatusCa
che(StatusCacheFactory.java:154)
  at com.ibm.ws.management.status.StatusCacheFactory.getStatusCa
che(StatusCacheFactory.java:97)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.initia
lizeProfileCR(AdminAgentMBeanProxy.java:1134)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.initia
lizeProfilePrivate(AdminAgentMBeanProxy.java:436)
If the server being registered to the administrative subsystem
is a DMZ Secure Proxy Server for IBM WebSphere Application
Server, the following FFDC may also be seen:
FFDC Exception:java.lang.ClassNotFoundException SourceId:com.ibm
.ws.management.status.NodeAgentStatusCache.requestReport ProbeId
:110 Reporter:com.ibm.ws.management.status.NodeAgentStatusCache
java.lang.ClassNotFoundException: com.ibm.ws.webservices.admin.s
tatus.NodeAgentStatusCacheExtension
  at java.lang.Class.forNameImpl(Native Method)
  at java.lang.Class.forName(Class.java:136)
  at com.ibm.ws.management.status.NodeAgentStatusCache.createSta
tusCacheExtensions(NodeAgentStatusCache.java:124)
  at com.ibm.ws.management.status.AbstractStatusCache.<init>(Abs
tractStatusCache.java:291)
  at com.ibm.ws.management.status.NodeAgentStatusCache.<init>(No
deAgentStatusCache.java:100)
  at com.ibm.ws.management.status.StatusCacheFactory.getStatusCa
che(StatusCacheFactory.java:154)
  at com.ibm.ws.management.status.StatusCacheFactory.getStatusCa
che(StatusCacheFactory.java:97)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.initia
lizeProfileCR(AdminAgentMBeanProxy.java:1134)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.initia
lizeProfilePrivate(AdminAgentMBeanProxy.java:436)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.access
$000(AdminAgentMBeanProxy.java:184)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy$1.run(
AdminAgentMBeanProxy.java:416)
  at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextMa
nagerImpl.java:4562)
  at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(Con
textManagerImpl.java:4650)
  at com.ibm.ws.management.component.AdminAgentMBeanProxy.initia
lizeProfile(AdminAgentMBeanProxy.java:413)
Aside from the stack trace which displays in the log, there is
no harm.

Problem conclusion

The code has been modified such that, in an administrative agent
process, the repository is not consulted to determine if the
subsystem being administered is a DMZ Secure Proxy Server for
IBM WebSphere Application Server.  The fix for this APAR
is currently targeted for inclusion in Service Level (Fix Pack)
of WebSphere Application Server version 7.0 (7.0.0.5).
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg2700498

Temporary fix

Comments

APAR Information

APAR number
PK87672
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-01
Closed date
2009-06-09
Last modified date
2009-06-09

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
WEBS APP SERV N
Fixed component ID
5724H8800

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:
25 October 2021

Tips

PK87672: METADATANOTAVAILABLEEXCEPTION WHEN RESGISTERING A PROFILE TO THE ADMINISTRATIVE AGENT.

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?