IBM Support

PH59488: NOT AUTOMATICALLY RESTART THE APPLICATION AFTER GROUP ROLLOUT COMPLETED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Not automatically restart the application after group rollout
    completed
    
    Scenario:
    Ran the rollout with Group rollout.
    
    Then, the rollout has been completed and the application "test
    edition 1" was changed to inactive condition and "test edition
    2" was changed to active condition.
    
    But, the "test edition 1" was not stopped and "test edition 2"
    was not started.
    
    So, they needed to stop the "test edition 1" and start the "test
    edition 2" manually to ready with the new edition.
    
    This works fine 8.5.5.13 but not in 8.5.5.21.
    

Local fix

  • No work-around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: New web application edition does not    *
    *                      automatically start after rollout of an *
    *                      application edition for a stand-alone   *
    *                      application server                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When rolling out a new edition of an application, the previous
    edition of Web application was not stopped and the new edition
    of
    Web application was not automatically started (despite being
    activated).
    If the application is identified as web application, rollout
    skips stopping the old application and starting the new one.
    

Problem conclusion

  • The issue was specific to stand-alone application server and
    not dynamic/static cluster rollouts. In this case, a stand-
    alone application server was erroneously treated as a web
    server and as a result the current edition of application was
    not stopped and consequently the new edition not started.
    Code changes were made to rectify the issue.
    
    The fix for this APAR is targeted for inclusion in fix packs
    9.0.5.19 and 8.5.5.26. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH59488

  • 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

    2024-01-30

  • Closed date

    2024-03-18

  • Last modified date

    2024-03-18

  • 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

[{"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.5","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
19 March 2024