IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * 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 being copied under the correct
    parent node.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.12 and 8.5.5.8.  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

    PI41707

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-25

  • Closed date

    2015-09-08

  • Last modified date

    2015-09-08

  • APAR is sysrouted FROM one or more of the following:

    PI37284

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022