PI53304: Auto scaling does not fully scale in to the minimum number of se rvers or scale out to the maximum number of servers

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When using auto scaling in Liberty profile, the scaling
  controller does not fully scale in to the minimum number of
  servers or scale out to the maximum number of servers.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile- Virtual             *
  *                  Enterprise/IM Component                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Auto scaling does not fully scale in to *
  *                      the minimum number of servers or scale  *
  *                      out to the maximum number of servers    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using auto scaling in Liberty profile, the scaling
  controller does not fully scale in to the minimum number of
  servers or scale out to the maximum number of servers.
  

Problem conclusion

• When there are multiple scaling members on a host, one is
  elected to be the leader which sends resource usage data to the
  scaling controller.  When the leader is stopped, the other
  scaling members do not properly dispose of control structures
  related to that leader.  This can result in resource usage data
  not being reported correctly to the scaling controller.  The
  code has been corrected so that the scaling members properly
  handle the stopping of the leader.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.9.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP