PI41588: BEST ROUTING RULES NOT ALWAYS FOUND WHEN USING GENERIC SERVER CLUSTER ROUTING POLICIES

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.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

• For WebSphere Application Server V7 and V8.5.
  
  When using Generic Server Cluster Routing Policies with
  default routing rules the best match is not always found when
  multiple work classes match the request with overlapping URIs
  and matching context roots. For example, if there are policies
  for URI=/* and URI=/XYZ/* a request may be matched to URI=/*
  rather than URI=/XYZ/*.  The end result is that the request
  may return a 500 result generated from the ODR.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server Intelligent    *
  *                  Management users with multiple workclasses  *
  *                  for generic server clusters with            *
  *                  overlapping URIs.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: On Demand Router returns 500 return     *
  *                      code for requests to generic server     *
  *                      clusters.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using Generic Server Cluster Routing Policies with
  default routing rules the best match is not always found when
  multiple work classes match the request with overlapping URIs
  and matching context roots. For example, if there are policies
  for URI=/* and URI=/XYZ/* a request may be matched to URI=/*
  rather than URI=/XYZ/*.  The end result is that the request
  may return a 500 result generated from the ODR.
  

Problem conclusion

• A fix has been provided to corrected the selection to the best
  matching URI in all cases including when there are multiple
  multiple generic server applications with overlapping
  URIs and identical context roots defined in the routing
  rules in multiple work classes.
  

Temporary fix

Comments

APAR Information

• 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