PK74565: COM.IBM.WEBSPHERE.MANAGEMENT.EXCEPTION.DOCUMENTNOTFOUNDEXCEPTION FOR CELLS/<CELL-NAME>/NODES/DEFAULTNODE/NODE-METADATA.PROPERTIES

Fixes are available

APAR status

Closed as program error.

Error description

If trace level is finest for com.ibm.ws.management.status, then
the following exception may be seen in the JVM SystemOut log:
com.ibm.websphere.management.exception.DocumentNotFoundException
  : cells/<cell-name>/nodes/DefaultNode/node-metadata.properties
    at com.ibm.ws.management.repository.FileRepository
      .extractInternal
    at com.ibm.ws.management.repository.FileRepository.extract
    at com.ibm.ws.management.repository.FileRepository.extract
    at com.ibm.ws.management.repository.FileRepository.extract
    at com.ibm.ws.management.repository.client
      .LocalConfigRepositoryClient.extract
    at com.ibm.ws.management.metadata
      .ManagedObjectMetadataAccessorImpl.extractMetadata

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  v7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: A DocumentNotFoundException may occur   *
*                      for file .../node-metadata.properties   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If trace level is finest for com.ibm.ws.management.status, then
the following stack trace may be seen in the Deployment Manager
or base Application Server SystemOut JVM log:

com.ibm.websphere.management.exception
.MetadataNotAvailableException: Could not obtain managed object
metadata from Config Repository.
at com.ibm.ws.management.metadata.
 ManagedObjectMetadataAccessorImpl.extractMetadata
at com.ibm.ws.management.metadata.
 ManagedObjectMetadataAccessorImpl.getMetadataProperties
at com.ibm.websphere.management.metadata.
 ManagedObjectMetadataHelper.isNodeZOS
at com.ibm.ws.management.status.AbstractStatusReport.
 _getServerType
at com.ibm.ws.management.status.AbstractStatusReport.
 getAppState
at com.ibm.ws.management.status.AbstractStatusReport.
 generateAppState
at com.ibm.ws.management.status.AbstractStatusReport.generate
at com.ibm.ws.management.status.AppServerStatusCache._sendReport
at com.ibm.ws.management.status.AppServerStatusCache._sendReport
at com.ibm.ws.management.status.AbstractStatusCache
  $StatusCacheRefreshThread.runPrivate
at com.ibm.ws.management.status.AbstractStatusCache
  $StatusCacheRefreshThread.run

Caused by: com.ibm.websphere.management.exception.
  DocumentNotFoundException: cells/<cell-name>/nodes/
    DefaultNode/node-metadata.properties
at com.ibm.ws.management.repository.FileRepository.
  extractInternal
at com.ibm.ws.management.repository.FileRepository.extract
at com.ibm.ws.management.repository.FileRepository.extract
at com.ibm.ws.management.repository.FileRepository.extract
at com.ibm.ws.management.repository.client.
  LocalConfigRepositoryClient.extract
at com.ibm.ws.management.metadata.
  ManagedObjectMetadataAccessorImpl.extractMetadata

An attempt was made to fetch node-metadata.properties from
the repository for the application for which status is
being reported even though the application is not deployed to
any server or node in the cell since it is a system application.

Problem conclusion

The code has been modified to not attempt to fetch
node-metadata.properties from the repository for system
applications which are not deployed to the node.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.3.  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
PK74565
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
2008-10-27
Closed date
2008-11-04
Last modified date
2008-11-04

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

Tips

PK74565: COM.IBM.WEBSPHERE.MANAGEMENT.EXCEPTION.DOCUMENTNOTFOUNDEXCEPTION FOR CELLS/<CELL-NAME>/NODES/DEFAULTNODE/NODE-METADATA.PROPERTIES

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?