Considerations for using return addresses
 Technote (troubleshooting)
 
Problem(Abstract)
Because resources are a limiting factor in a programming environment, the proper use of return addresses provide a sufficient amount of available resources.
 
Cause
Each unique return address uses an IP address from the addresses available on the subnet. Each return address has a limited number of ports that can be used to create sockets.
 
Resolving the problem
When you use Net Address Translation (NAT) or kernel content based routing (kcbr) forwarding methods, you must define a return address for communication between Load Balancer and the back-end servers.
The number of connections that Load Balancer can keep active with the back-end server is limited by the number of return addresses that are defined. Load Balancer uses ports that are based upon the return address only; not the return address and server combination. When all the available ports are in use, additional connections fail.

In a busy environment, use multiple return addresses to prevent a shortage of available ports.
 
Related information
Version 6.1 Release Notes
 
 
Cross Reference information
Segment Product Component Platform Version Edition
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): Windows
Software version: 6.1
Software edition:
Reference #: 1242116
IBM Group: Software Group
Modified date: Jul 19, 2006