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
APAR status
Closed as program error.
Error description
Load Balancer for ipv4 and ipv6 crash with call stack containing: #3 os_memalloc #4 _lbsel_ct_getnewcr #5 _lbha_handlereprecords #6 _lbha_event #7 lbhahb_pbuf_entry
Local fix
The customer may see relief from crash if they temporarily change the repstrategy to replicate connection records only. There is a little loss of function with this workaround but it might be less impact than the unexpected crash.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Load * * Balancer for IPv4 and IPv6 high * * availability users with affinity * * replication * **************************************************************** * PROBLEM DESCRIPTION: The backup Load Balancer for ipv4 and * * ipv6 crashing during a memory * * allocation of an affinity record. * **************************************************************** * RECOMMENDATION: * **************************************************************** Executor consuming excessive memory and eventual crash from failed memory allocation.
Problem conclusion
The backup load balancer was not removing expired affinity records properly which lead to memory allocation failures and a crash of the executor. Fix levels: 8.5.5.13 9.0.0.5
Temporary fix
Comments
APAR Information
APAR number
PI84336
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-11
Closed date
2017-08-10
Last modified date
2018-06-08
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
Document Information
Modified date:
04 May 2022