Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
Problem Description: The "Sub-state" in the hamon.log for Load Balancer for IPv4 and IPv6 (uLB) remains as "Not Synchronized". Recreation Steps: Configure HA and set the loglevel to 5. You'll see the "Sub-state ..................... Not Synchronized" in the hamon.log --- For example, Jun15 12:49:01.301 NZST HAM: Got action value from state machine. Action ........................ noOp Old executor status: com.ibm.internet.nd.server.SRVHaInfo@2039f39f Status ........................ Valid Mode .......................... Single Address ....................... 10.200.138.67 Role .......................... primary Strategy ...................... auto State ......................... Active Sub-state ..................... Not Synchronized --- Proposed Solution: Remove the "Sub-state" because the "dscontrol hi status" does not have the "Sub-state" in the uLB.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Edge Load * * Balancer for ipv4 and ipv6 users * **************************************************************** * PROBLEM DESCRIPTION: When using the High Availibity * * function and running with increased * * loglevel, the Sub-state will always * * show as Not Synchronized * **************************************************************** * RECOMMENDATION: * **************************************************************** The high availibity sub-state always shows at Not Synchronized in the log file.
Problem conclusion
Sub-state is not a function of the Load Balancer for ipv4 and ipv6. It is an old artifact from the previous product, Load Balancer for ipv4. It has been removed from the Load Balancer for ipv4 and ipv6 logfile. Fix level : 7.0.0.42 8.0.0.13 8.5.5.11 9.0.0.2 Does not affect the Load Balancer for ipv4 release since sub-state is a valid function of high availability.
Temporary fix
Comments
APAR Information
APAR number
PI64471
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
2016-06-21
Closed date
2016-08-02
Last modified date
2016-08-02
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
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022