IBM Support

PI34283: WEBSPHERE CLUSTER STATUS HANGS IN PARTIAL STATE OR FAILS WHEN RIPPLESTARTED FROM A STOPPED STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When rippleStart is attempted on a cluster in a stopped state,
    the cluster will hang in partial state for the full length of
    ripplestart notification time-out (default time of 5 minutes).
    A check is not done to see if all members are up and running
    even if the cluster member starts successfully before the
    timeout setting triggers. Other cluster administrative
    processes cannot be performed during this time period.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 rippleStart                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: rippleStart hangs when attempted from   *
    *                      stopped state after all cluster         *
    *                      members have started                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a rippleStart is attempted on a WebSphere Application
    Server cluster which is in a stopped state, the cluster status
    will hang in a partially started state despite cluster members
    having started successfully. This is due to the rippleStart
    notification timeout (set by IBM_CLUSTER_NOTIFICATION_TIMEOUT)
    not being interrupted during a member start step of
    rippleStart. This causes the rippleStart process to last the
    length of the timeout value, even if members have completed
    ripple starting. Other attempts to start administrative
    processes are also blocked during this time.
    

Problem conclusion

  • The member which is attempted to be rippleStarted is declared
    before the stopping of any of the members is attempted.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.5.  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

    PI34283

  • 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

    2015-02-05

  • Closed date

    2015-02-12

  • Last modified date

    2015-02-12

  • 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":"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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022