PM82872: DOCUMENTNOTFOUNDEXCEPTION WHEN CHECKING APPLICATION STATUS TO ADMINAGENT

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• If multiple nodes are managed by adminagent and you try to
  check the existing application status via wsadmin command, the
  wsadmin command might fail to get the application distribution
  status
  
  wsadmin>$AdminApp isAppReady query
  ADMA5071I: Distribution status check started for application
  query.
  ADMA5011I: The cleanup of the temp directory for application
  query is complete.
  ADMA5072I: Distribution status check completed for application
  query.
  WASX7015E: Exception running command: "$AdminApp isAppReady
  query";
  exception information: com.ibm.ws.scripting.ScriptingException:
  Failure in getting application distribution status.
  
  When the exception occurrs, you can see a
  DocumentNotFoundException in adminagent's SystemErr.log.
  
  [13/02/07 21:29:39:725 JST] 00000023 SystemErr     R
  com.ibm.websphere.management.exception.DocumentNotFoundException
  : cells/Cell01/nodes/Node02/node-metadata.properties
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0, V8.0 and v8.5                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When checking for application status    *
  *                      using the wsadmin isAppReady command    *
  *                      on an admin agent environment with      *
  *                      multiple registered nodes, the wsadmin  *
  *                      command may fail to get the             *
  *                      application                             *
  *                      distribution status.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When checking for application status using the wsadmin
  isAppReady command on an admin agent environment with multiple
  registered nodes, the wsadmin command may fail to get the
  application distribution status with the
  DocumentNotFoundException on the second node. For example:
  wsadmin>$AdminApp isAppReady query
  ADMA5071I: Distribution status check started for application
  query.
  ADMA5011I: The cleanup of the temp directory for application
  query is complete.
  ADMA5072I: Distribution status check completed for application
  query.
  WASX7015E: Exception running command: "$AdminApp isAppReady
  query";
  exception information: com.ibm.ws.scripting.ScriptingException:
  Failure in getting application distribution status.
  

Problem conclusion

• The wsadmin isAppReady command has been fixed to correctly get
  the application distribution status on all nodes.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.39, 8.0.0.7 and 8.5.5. 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 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

• R800 PSY

     UP

• R850 PSY

     UP