Fixes are available
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.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 returns 503s after application edition rollout when node based ARFM is selected
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WAS ND edition- Virtual * * Enterprise/IM Component * **************************************************************** * PROBLEM DESCRIPTION: ODR returns 503s after application * * edition roll-out when node based ARFM * * is enabled * **************************************************************** * RECOMMENDATION: * **************************************************************** When using node based ARFM and application edition roll-out that involves a hard-reset, group roll-out may result in subsequent application requests failing with a 503 from the ODR. Restarting the ODR corrects the issue so that application requests will once again be routed successfully.
Problem conclusion
The On Demand Router (ODR) code was changed to ensure that the new application edition is used when managing and collecting node based ARFM statistics. Prior to this change the node based ARFM objects were keeping a reference to the previous application edition which caused the ODR logic to incorrectly reference this old edition when attempting to route requests. Because the old edition had quiesced the servers it still thought the servers were unavailable for routing and this caused the ODR routing logic to return the 503s. This code has been updated to remove references to the old edition from the node based ARFM objects which allows the routing logic to work with the new, correct edition and successfully route the request to available servers. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.10. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Do not use application edition roll-out that involves a hard- reset, group roll-out while using node based ARFM. If the problem is encountered as a result of such an application edition roll-out then restart the On Demand Router to allow requests to flow normally again.
Comments
APAR Information
APAR number
PI58594
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-04
Closed date
2016-05-20
Last modified date
2016-05-20
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022