PI37284: DATA CORRUPTION IN COPIED TREE BECAUSE WHEN MATERIALIZING, THE CHILD IS BEING LINKED TO THE WRONG PARENT

APAR status

• Closed as program error.

Error description

• DATA CORRUPTION IN COPIED TREE BECAUSE WHEN MATERIALIZING, THE
  CHILD IS BEING LINKED TO THE WRONG PARENT
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server        *
  *                  Feature Pack for XML users                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Data corruption in copied tree due to   *
  *                      a child node being linked to the        *
  *                      wrong parent node.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the process of materializing a copied node, we inspect
  whether we have made a copy of the preceding node. If there is
  no direct copy then we perform a deep lookup to see if we have
  a copy of it's original node recursively until we find one or
  we reach a node that's not a copy of any node. This operation
  will return the wrong node as the copy of the preceding node
  if one of the original nodes was already copied under a
  different node within the same tree. The parent node is
  retrieved using the returned node, resulting in the child node
  we just copied being added to the wrong parent. This can cause
  an ArrayIndexOutOfBoundsException in the
  FastAccessMediator.getInternalFastAccess method.
  

Problem conclusion

• The algorithm was corrected to determine whether the returned
  node is in fact the copy of preceding node by comparing the
  parent nodes. If it's not a copy, then the copy routine is
  invoked again with a flag to avoid deep lookup. This will
  result in the preceding node to be copied under the correct
  parent node.
  
  The fix for this APAR is currently targeted for inclusion in
  Feature Pack for XML 1.0.0.17. 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:

  PI41707

Fix information

• Fixed component name

  XML FEATUREPACK

• Fixed component ID

  5724J0856

Applicable component levels

• R700 PSY

     UP