Fixes are available
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
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
The WebSphere Application Server Load Balancer for IPv4 and IPv6 should record information about the cause of a highavailability takeover.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Load Balancer for IPv4 and * * IPv6 users * **************************************************************** * PROBLEM DESCRIPTION: Provide reason for takeovers when a * * high availability failover occurs. * **************************************************************** * RECOMMENDATION: * **************************************************************** The High Availability feature enables the backup to takeover when necessary but often the reason for the takeover is unknown. The user can find the reason for the takeover after applying this change.
Problem conclusion
When using the load balancer for ipv4 and ipv6, information is recorded in different locations depending on the operating system. The reason for a high availability takeover is recorded on the load balancer which assumed the active forwarding role and can be searched for based upon the string "HA TAKEOVER". On Windows, this information is recorded in the ibmlb2.log found in the dispatcher logs directory. The operating system may not show data in this log until the executor is stopped. On Linux, this information is recorded in /var/log/messages. On AIX, this information was previously stored in memory and could only be viewed if extracted from the executor using executor trace formatting and if extracted before the trace buffer filled and was overwritten. With this change, the information is written to syslog. It is written based upon KERN facility and with priority NOTICE; The syslog.conf should be updated to include this reporting if it is desired. Fix included in fixpacks 8.5.5.16 and 9.0.0.11.
Temporary fix
Comments
APAR Information
APAR number
PH07647
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
2019-01-24
Closed date
2019-01-31
Last modified date
2019-01-31
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
Document Information
Modified date:
28 April 2022