IBM Support

PM60134: DEFAULT ATTRIBUTES ARE BEING INCORRECTLY ADDED TO XML CONFIGURAT ION FILES DURING MIGRATION OF WEBSPHERE APPLICATION SERVER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During WebSphere Application Server migrations, various XML
    documents maybe getting updated with default attributes and
    tags that didn't exist in the source configuration.  These
    default attributes and tags can cause changes in behavior.
    Specifically, classloader and mode="PARENT_FIRST" elements
    have been known to be added, which in turn have caused various
    classloading problems at server and application runtime.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 migration.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Default attributes are being            *
    *                      incorrectly added to XML configuration  *
    *                      documents during WebSphere              *
    *                      Application Server migrations.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After performing a WebSphere Application Server migration
    there could be a change in the behavior of applications.  This
    is due to default attributes being added into XML
    configuration documents.  Most reported incidents have
    involved class loading issues where there has been a change
    from parent last to parent first class loading.
    

Problem conclusion

  • The WebSphere Application Server migration code now checks to
    see if default XML attributes were a part of the old WebSphere
    Application Server configuration documents before adding them
    to the new WebSphere Application Server configuration documents.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.4.  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

    PM60134

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-09

  • Closed date

    2012-03-21

  • Last modified date

    2012-03-21

  • 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

[{"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 October 2021