Fixes are available
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
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
When there are multiple web modules that match a request equally well (same context root, uri, and both either generic or non-generic applications), the web module is mapped to the less specific vhost and is sometimes selected when it is preferable to select the web module with the most specific vhost match. This routing mismatch causes the ODR to return a 404 error code. The preference for vhost matches from most specific to least specific is as follows: exact match on both host and port, host match with wildcard port, wildcard host with port match, wildcard host and wildcard port match.
Local fix
Ensure that there are no equivalent web module matches for incoming requests
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server On Demand Router * **************************************************************** * PROBLEM DESCRIPTION: An incoming request to the On Demand * * Router that matches multiple web * * modules with the same level of detail * * may be mapped to a web module with a * * less specific virtual host match. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a request arrives at the On Demand Router it is matched with a web module using the virtual host as well as context root, and uri mapping of the web module mapped to that virtual host. A request will always be routed to the most specific web module context root and uri mapping. However, if the context root and uri mapping of multiple web modules are equal the request should be routed to the web module mapped to the most specific virtual host match. In the error case the web module selected was the first virtual host match with the most specific context root and uri mapping from the web module rather than the most specific virtual host map.
Problem conclusion
The problem code was corrected to select the most specific virtual host match when there are multiple equally good web module matches using context root and uri pattern. The most specific virtual host is selected using this criteria in descending order: (1) exact match on host and port, (2) exact match on host and wildcard on port, (3) wildcard on host and exact match on port, and (4) wildcard on host and wildcard on port The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.12. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Eliminate duplicate web module matches by providing more specific context root and uri mappings such that requests will match more specifically to only one web module.
Comments
APAR Information
APAR number
PI78774
Reported component name
WAS VIRTUAL ENT
Reported component ID
5725C9203
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-24
Closed date
2017-05-11
Last modified date
2017-05-11
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:
03 May 2022