Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
ODR may route requests to the wrong GSC when RulesOverAffinity is set. Lets's assume that there are two GSCs running different applications in an ODR cell: GSC1 has members hosting application A(with context root /A) and GSC2 has members hosting application B with context root(/A/B). Let's also assume that the ODR routing rules are configured appropriately. The sequence of events demonstrating the problem is given below: A request, /A/B/Ping, is made to application B(which is sent to GSC2). Application B responds with its affinity cookie JSESSIONIDB. A different request, /A/Ping, is made targetting application A. If a member of GSC1 is down and this request were to go to that as part of the load balancing algorithm, then a retry is triggered to select a different server. However, during the retry the request is sent to GSC2 member instead of another GSC1 member because of the affinity cookie, JSESSIONDB.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of WVE 7.0.0.4 and lower * * versions are affected by this behaviour. * **************************************************************** * PROBLEM DESCRIPTION: As mentioned in the error * * description, a wrong server is chosen * * during retry. This will result in an * * incorrect routing behaviour. * **************************************************************** * RECOMMENDATION: * **************************************************************** This problem was due to improper handling of RulesOverAffinity for the request during a retry attempt to select another member in the same cluster.
Problem conclusion
Changes have been made to handle RulesOverAffinity properly during retry attempt. This issue will be resolved in the next available fix pack for WebSphere Virtual Enterprise V.7.0.0.
Temporary fix
Comments
APAR Information
APAR number
PI13499
Reported component name
WAS VIRTUAL ENT
Reported component ID
5725C9203
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-11
Closed date
2014-06-17
Last modified date
2014-06-17
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
WAS VIRTUAL ENT
Fixed component ID
5725C9203
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
27 April 2022