PM82470: APPLICATION EDITION FAILS TO CLEAN UP STATE WHEN ROLLOUT FROM VALIDATE STATE FAILS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • App edition fails to clean up state when rollout from validate
    state fails
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users managing application              *
    *                  editions with WebSphere Virtual             *
    *                  Enterprise                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: The application edition state is not    *
    *                      recovered correctly after a rollout     *
    *                      failure.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following issues are reported:
    * The rollout incorrectly continues if an appliction or server
    fails to start in the first group.
    * If a timeout occurs during a group rollout, the application
    edition state on each server is not fully recovered.
    * If an error occurs during a group rollout, the application
    edition state on each server is not fully recovered.
    * An application edition extension task
    (AppEditionInitializerExtTask) incorrectly reports exceptions
    resuling in failures during the Virutal Enterprise profile
    creation.
    * When rolling out an edition from validate state, any
    failures leave the edition in unexpected state.  Instead of
    reverting to the validate state, an edition goes into
    inactive state if a rollout failure occurs.  The edition is
    associated with the original target cluster instead of the
    validation cluster.
    * If a validate rollout is performed with an application that
    contains an EJB and web module, and if the current edition has
    ony a web module, then the validate edition has no target
    (cluster) specified for the EJB module.
    

Problem conclusion

  • Code changes were made to resolve the listed issues.
    
    This fix will be included in the next available fix pack for
    WebSphere Appliation Server Version 8.5, WebSphere Virtual
    Enterprise Version 7.0, and WebSphere Virtual Enterprise
    Version 6.1.1.
    For information about recommended updates, check:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82470

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-08

  • Closed date

    2013-02-08

  • Last modified date

    2013-05-02

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

    PM75625

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
General

Software version:

850

Reference #:

PM82470

Modified date:

2013-05-02

Translate my page

Machine Translation

Content navigation