Traffic not forwarding using Load Balancer's Content Based Routing (CBR) configuration in conjunction with Caching Proxy
 Technote (FAQ)
 
Problem
Traffic is not forwarded after following instructions in the Load Balancer Administration Guide to define a CBR configuration. Tracing from Caching Proxy shows an error from the calls to CBR.
 
Cause
The Load Balancer's CBR component was redesigned in Edge Component release 5.0 and higher. The new design makes CBR more consistent with the Caching Proxy configuration and allows CBR to work with WebSphere® Application Server.

With this new configuration, the cluster must be defined using the same hostname or IP that the incoming request contains. A match is performed between the CBR cluster and the host header on the inbound request. For example, if the request enters as the IP address, the cluster must be defined as the IP address. If there is more than one hostname that resolves to a single IP address and requests arrive with any one of those hostnames, all the hostnames must be defined as clusters.
 
Solution
Clusters defined in CBR must be defined to match the incoming request.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
237390
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1192762
IBM Group: Software Group
Modified date: Sep 3, 2007