In Load Balancer configurations, a collocated client might not work
 Technote (troubleshooting)
 
Problem(Abstract)
Clients located on the same machine as Load Balancer might not function correctly. This is not a supported environment for most versions of Load Balancer.
 
Cause
Load Balancer uses different techniques to examine the incoming packets on the various operating systems that it supports. In most cases, Load Balancer does not receive packets from the local machine. It receives packets coming from the network only. As a result, requests that are made to the cluster address from the local machine are not received by Load Balancer and cannot be serviced.
 
Resolving the problem
For the Dispatcher component of Load Balancer, support of a collocated client configuration has been added to the following versions of Load Balancer installations that run on Linux® systems:
  • V6.0.1.5 or later
  • V5.1.1.29 or later
  • V5.0.2.50 or later

When Load Balancer is capable of forwarding requests from a collocated client, Load Balancer will not forward a request if the source IP address is the same as the cluster IP address. If Load Balancer forwarded requests from collocated clients, Load Balancer would constantly forward the client requests and cause a networking loop. You must bind the local application to an IP address that is not in the cluster.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Edge Server Load Balancer Multi-Platform Edge Server 2.0 GA, Edge Server 2.0 NLV, Edge Server 2.0.x
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): AIX
Software version: 6.0.2
Software edition:
Reference #: 1210238
IBM Group: Software Group
Modified date: Jun 27, 2005