IBM Support

PI84190: LOAD BALANCER MANAGER CONSUMES UNNECESSARY MEMORY RETAINING WEIGHT HISTORY

Fixes are available

9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The function which used this history no longer exists and could
    be a potential cause of memory growth.
    

Local fix

  • Edit dsserver and change the last line to add the custom
    property -DLB_DONT_KEEP_SERVER_HISTORY=true. LB will need to be
    restarted (executor stopped, dsserver stopped) for this to take
    effect.
    
    Example:
    export LIBPATH=$LB_BASE/servers/lib
      /opt/IBM/WebSphere/Edge/ULB/java/jre/bin/java -cp
    $LB_CLASSPATH
    $LB_INSTALL_PATH $LB_CLIENT_KEYS $LB_SERVER_KEYS $LB_BINDIR2
    -DLB_DONT_KEEP_SERVER_HISTORY=true
    -Djava.rmi.server.hostname=127.0.0.1
    -Djava.protocol.handler.pkgs=com.ibm.net.ssl.internal.www.protoc
    ol
    com.ibm.internet.nd.server.SRV_KNDConfigServer $LB_RMIPORT
    $LB_LOGDIR
    $LB_SAVEDIR $LB_BINDIR $LB_CONFIGFILE $LB_RMISERVERPORT &
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere APplication Server Edge       *
    *                  Components Load Balancer Manager function   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The load balancer manager function      *
    *                      may consume unnecessary memory.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The manager function stores history of the server weights but
    never utilizes this data. When using a large configuration,
    this extra memory usage may impact performance.
    

Problem conclusion

  • Disabled retaining the weight history. It can be enabled by
    adding the custom property -DLB_KEEP_SERVER_HISTORY=true in
    the dsserver(cbrserver or ssserver) script.
    
    Fix level: 8.5.5.13 and 9.0.0.5
    Older levels can disable this memory usage by setting the
    custom property -DLB_DONT_KEEP_SERVER_HISTORY=true in dsserver
    (ssserver or cbrserver).
    
    The server (dsserver, ssserver, cbrserver) must be restarted
    for the java property to take effect.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI84190

  • Reported component name

    WS EDGE LB IPV4

  • Reported component ID

    5724H8812

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-07

  • Closed date

    2017-07-11

  • Last modified date

    2017-07-11

  • 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

    WS EDGE LB IPV4

  • Fixed component ID

    5724H8812

Applicable component levels

  • R850 PSY

       UP

  • R900 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:
04 May 2022