APAR status
Closed as program error.
Error description
There is an issue with the current scoring scheme when the
following scenario is present.
Example:
Request of
http://hostname/abc/login.jsp
<UriGroup Name="URI_1">
<Uri AffinityCookie="JSESSIONID"
AffinityURLIdentifier="jsessionid" Name="*.jsp"/>
</UriGroup>
<UriGroup Name="URI_2">
<Uri AffinityCookie="JSESSIONID"
AffinityURLIdentifier="jsessionid" Name="/abc/*"/>
</UriGroup>
According to our current scheme, both URI groups would produce
the same score, and would result in sending the request to the
first one found. Given the request above, it's obvious that it
should be handled by the Cluster associated to URI Group URI_2.
Local fix
Manually edit the plugin-cfg.xml file to switch the order of the
URI group so the correct server is picked first.
Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server *
* webserver plug-ins. *
****************************************************************
* PROBLEM DESCRIPTION: Plug-in routes requests to servers by *
* matching incoming URIs with the URI *
* patterns in plugin-cfg.xml. When an *
* incoming URI matches multiple URI *
* patterns that having the same score, *
* plug-in picks up the first match. *
* *
* While this matching methodology works *
* in most cases, however, it could *
* sometimes make plug-in pick up an *
* unintended server. For example, both *
* URI patterns "*.jsp" and "/ab/*" *
* match the URI "/ab/test.jsp", and *
* both patterns score 4. The second *
* pattern is preferred over the second. *
* Under current design, the pattern *
* listed first will be picked, which *
* sometimes could cause unexpected *
* result. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Incoming requests sometimes were not routed to target servers
due to problems in pattern matching.
Problem conclusion
This APAR addressed this problem by doing more specific
pattern matching before wild card character. The fix will be
available in WAS 5.0.2.16, 5.1.1.9, and 6.0.2.7 service packs.
Temporary fix Comments
APAR information |
APAR number |
PK14635 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-11-04 |
Closed date |
2005-12-29 |
Last modified date |
2006-02-05 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|