PM79257: addNode -asExistingNode displays exceptions

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
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
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When creating a cell from a template cell as described at
  
  http://www14.software.ibm.com/webapp/wsbroker/redirect?version=m
  att&product=was-nd-dist&topic=tagt_addNode_asExistingNode ,
  
  DocumentNotFound exceptions are displayed with path
  names  containing a "blas" or "cus" folder, followed by
  a "successfully federated" message at the end of the addNode
  operation.
  
  The exceptions do not prevent successful federation.  This
  change removes them.
  

Local fix

• The "DocumentNotFoundException" and path names  containing a
  "blas" or "cus" folder messages can be ignored as they are
  benign.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Network Deployment edition Version   *
  *                  8.0 and 8.5 using addNode -asExistingNode.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When creating a cell from a template    *
  *                      cell, some DocumentNotFound exceptions  *
  *                      might be displayed.                     *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  When creating a cell from a template  cell, some
  DocumentNotFound exceptions might be displayed, followed by
  successful completion of addNode, as shown below:
  .....
  ADMU0016I: Synchronizing configuration between node and cell.
  com.ibm.wsspi.management.bla.op.OpExecutionException:
  CWWMH0121E: Could not read configuration data for composition
  unit "WebSphere:cuname=isclite,cuedition=BASE".  Error data:
  com.ibm.websphere.management.exception.DocumentNotFoundException
  :
  com.ibm.websphere.management.exception.DocumentNotFoundException
  : cells/myCell/cus/isclite/cver/BASE/cu.xml
  at
  com.ibm.ws.management.bla.model.CompositionUnitConfig.read(Compo
  sitionUnitConfig.java:499)
  at
  com.ibm.ws.management.bla.model.CompositionUnitFactoryImpl.readC
  ompositionUnitFromCompositionUnitURI(CompositionUnitFactoryImpl.
  java:199)
  at
  com.ibm.ws.management.bla.sync.DefaultObjectHelper.loadObject(De
  faultObjectHelper.java:490)
  at
  com.ibm.ws.management.bla.sync.DefaultObjectHelper.loadObject(De
  faultObjectHelper.java:395)
  at
  com.ibm.ws.management.bla.sync.DefaultObjectHelper.createAndLoad
  ForRepositoryOpDone(DefaultObjectHelper.java:340)
  at
  com.ibm.ws.management.bla.framework.DefaultSyncHandler.collectOb
  jectsFromCU(DefaultSyncHandler.java:261)
  at
  com.ibm.ws.management.bla.framework.DefaultSyncHandler.repositor
  yOpDone(DefaultSyncHandler.java:193)
  at
  com.ibm.ws.management.bla.sync.BLABinaryProcessor.postProcess(BL
  ABinaryProcessor.java:541)
  at
  com.ibm.ws.management.bla.sync.BLABinaryProcessor.handleNotifica
  tion(BLABinaryProcessor.java:497)
  at
  com.ibm.ws.management.sync.NodeSync.sendLocalEvent(NodeSync.java
  :775)
  at
  com.ibm.ws.management.sync.NodeSync.sendCompletionEvent(NodeSync
  .java:803)
  at
  com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java
  :356)
  at
  com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:15
  7)
  at java.lang.Thread.run(Thread.java:770)
  Caused by:
  com.ibm.websphere.management.exception.DocumentNotFoundException
  :
  com.ibm.websphere.management.exception.DocumentNotFoundException
  : cells/btiffanyCell07/cus/isclite/cver/BASE/cu.xml
  at
  com.ibm.ws.management.bla.util.Util.extractDocUriAsSystem(Util.j
  ava:678)
  at
  com.ibm.ws.management.bla.model.CompositionUnitConfig.read(Compo
  sitionUnitConfig.java:479)
  ... 13 more
  Caused by:
  com.ibm.websphere.management.exception.DocumentNotFoundException
  : cells/btiffanyCell07/cus/isclite/cver/BASE/cu.xml
  at
  com.ibm.ws.management.repository.FileRepository.extractInternal(
  FileRepository.java:1146)
  at
  com.ibm.ws.management.repository.FileRepository.extract(FileRepo
  sitory.java:1127)
  at
  com.ibm.ws.management.repository.FileRepository.extract(FileRepo
  sitory.java:1078)
  at
  com.ibm.ws.management.repository.FileRepository.extract(FileRepo
  sitory.java:1067)
  at
  com.ibm.ws.management.bla.util.Util._extractDocUri(Util.java:689
  )
  at com.ibm.ws.management.bla.util.Util.access$100(Util.java:77)
  at com.ibm.ws.management.bla.util.Util$2.run(Util.java:672)
  at
  com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
  Impl.java:5445)
  at
  com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(Conte
  xtManagerImpl.java:5536)
  at
  com.ibm.ws.management.bla.util.Util.extractDocUriAsSystem(Util.j
  ava:670)
  ......
  ADMU0003I: Node btiffanyNode25 has been successfully federated.
  

Problem conclusion

• The exceptions were caused by attempts to delete documents
  in an area that would not be present after federation.  The
  code is changed so the problem no longer occurs.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.6 and 8.5.0.2. 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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP