PK76379: FFDC LOGS DOCUMENTNOTFOUNDEXCEPTION ON DEFAULT.COMPOSITE FILE AFTER DEPLOYMENT IN A NETWORK DEPLOYMENT ENVIRONMENT

SCA Feature Pack Fix Pack V1.0.0.1 for WebSphere Application Server V7.0 release
1.0.0.3: WebSphere Application Server V7 Feature Pack for SCA Fix Pack 1.0.0.3

APAR status

• Closed as program error.

Error description

• FFDC logs DocumentNotFoundException on default.composite file
  after deployment in a WebSphere Application Server Network
  Deployment environment. The exception occurs due to an attempt
  to access a file that has not been synchronized to the node
  yet. While this exception does not have runtime impact, it is
  still important to identify the issue with the repository
  synchrnoization window and prevent such FFDCs from occurring
  that can cause confusion.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server V7.0 Feature   *
  *                  Pack for SCA users who deploy applications  *
  *                  in multi-node configurations                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When deploying an SCA application in a  *
  *                      multi-node configuration, it is         *
  *                      possible that an error will be          *
  *                      logged in FFDC                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When deploying a Service Component Architecture (SCA)
  application in a multi-node environment, it is possible that a
  DocumentNotFoundException error will be logged in FFDC. This
  occurs when an action is triggered on a remote node when an
  SCANamingIndex.xml file is updated as part of application
  deployment. It is possible that when that action is triggered,
  the default.composite file that is required by the action will
  not have been synchronized to the remote node yet.
  
  This error message in FFDC has no direct functional impact, as
  the actual intent of the triggered function will be satisfied
  when it is run on the deployment manager node. The only issue
  here is the error being logged in FFDC.
  

Problem conclusion

• The action that is triggered by an SCANamingIndex.xml file
  update will no longer run on node agents or remote application
  servers.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 1.0.0.1 of the Feature Pack for SCA on WebSphere
  Application Server V7.0. 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

  WAS SCA FEATURE

• Fixed component ID

  5724J0854

Applicable component levels

• R700 PSY

     UP