IBM Support

PM13680: ADMA7024E MESSAGE INDICATING APPLICATION ERROR CAN OCCUR WHEN THE NODE AGENT IS RESTARTED DURING APPLICATION EXPANSION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application is deployed, the node synchronization
    process will install the application files in the nodeconfig. In
    the expansion phase, the <applname>.marker file is created in
    directory wstemp/appsync. If the Node Agent is stopped during
    the expansion phase, the marker file is not altered to indicate
    that a problem occurred, and expansion of the application files
    does not complete when the Node Agent is restarted.
    The marker file is created with a value of '0', indicating that
    the expansion is in progress, and is deleted after expansion
    completed successfully. If an error occurred, the marker file
    should contain a non-zero value, so the retry code running after
    the Node agent started would know that it has to complete the
    app expansion. In the failure case the marker file still existed
    and contained a value of zero, so expansion for this app did not
    continue.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Network    *
    *                  Deployment users of V7.0                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Failed application expansions are not   *
    *                      re-expanded.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Applications deployed in WebSphere Application Server
    environment are expanded to a binaries directory. If the
    expansion fails to complete in a Network Deployment
    environment, expansion is restarted in the next node
    synchronization cycle. Expansion restart is not triggered for
    some failures.
    

Problem conclusion

  • The fix will trigger expansion for all applications for which
    expansion previously failed.
    
    APAR PM13680 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.13 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM13680

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-04

  • Closed date

    2010-07-11

  • Last modified date

    2010-11-03

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

    PM11786

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK61114

       UP10/10/21 P F010

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022