IBM Support

PI59552: APPLICATION UPDATE CORRUPTED DEPLOYMENT.XML WITH INCORRECT APPCFG:APPLICATIONCONFIG REFERENCE.

Fixes are available

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the customer's application update is performed
    deployment.xml DD is corrupted.
    Steps to reproduce the problem:
    1. start deployment manager.
    2. deploy an ear file named SimpleMVC
    3. access to Applications > Application Types > WebSphere
    enterprise  applications > SimpleMVC > Session management >
    Custom properties
    4. update the ear file.
    
    The 3rd step is the trigger of the issue.
    
    The application update successfully, but in the SystemOut.log,
    we see the following error:
    ----------------------------------
    [3/14/16 1:16:14:173 PDT] 00000062 ConfigRootImp E   WSVR0232E:
    Unable to resolve cross document link identified by the uri:
    tempworkarea.xmi#ApplicationConfig_1457943347373, and referenced
    by document deployments/SimpleMVC/deployment.xml
    ----------------------------------
    With this corrupted xml, we cannot start the application from
    the administrative console.
    

Local fix

  • no workaround
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the administrative console to  *
    *                  configure session parameters in             *
    *                  applications.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: An invalid config stanza is             *
    *                      added to the deployment.xml of an       *
    *                      application when navigating through     *
    *                      session management panels.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The administrative console creates a config stanza that is
    invalid if the user navigates away from the application
    session management panels without making any changes.
    

Problem conclusion

  • With this fix, the console doesn't create the appconfig stanza
    until it is really needed which prevents the bad stanza from
    being written.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.10.  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

    PI59552

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-23

  • Closed date

    2016-05-24

  • Last modified date

    2016-05-24

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021