IBM Support

PI92265: SETTING ONE JVM OF MULTIPLE DYNAMIC CLUSTERS INTO MAINTENANCE MODE, FAILS FOR ALL DYNAMIC CLUSTERS EXCEPT FOR ONE.

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

  • When using multiple dynamic clusters, with each being
    configured with the criteria "minimum / maximum instances
    set
    to 1/1", the APC does successfully put the cluster member of
    one dynamic cluster into Maintenance Mode and starts an
    additional member to meet the criteria. For each additional
    dynamic cluster, the operation fails with the following
    sequence of events.
    a) CWMMS0468E -> The server maintenance mode operation timed
    out
    b) CWMMS0461E -> A server maintenance mode error occurred
    and
    the operation will be rolled back.
    c) CWMMS0448I -> Notifying the application placement
    controller
    (APC) of the server maintenance mode change to false ...
    d) CWMMS0465I -> The roll back of the server maintenance
    mode
    operation has completed successfully.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Putting multiple server instances, from *
    *                      multiple Dynamic clusters into          *
    *                      maintenance mode fails for all servers  *
    *                      except one                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Putting multiple server instances in maintanance mode across
    multiple dynamic clusters failed with message CWMMS0461E for all
    instances except one.  This was caused due to two factors; one
    being an intermittent issue of a race condition between threads
    which could prevent APC from acting upon the request and the
    second factor, a configuration issue, was a high value for APC
    property Minimum time between placement change which caused the
    pending maintanance mode request to time out.
    

Problem conclusion

  • Code was modified to resolve the race condition among threads
    for APC notification. It is also advisable to ensure the time
    out for maintenance mode exceeds the APC property, Minimum time
    between placement change.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.16.  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

    PI92265

  • 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

    2018-01-10

  • Closed date

    2019-04-30

  • Last modified date

    2019-04-30

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI92265

Modified date: 30 April 2019