Load balancer connection terminates unexpectedly
Check the following:
- Verify the load balancer administrator has not shut down the load balancer.
- Verify that TCP/IP connectivity still exists between the load balancer and the Advisor (for example, from the Advisor host, ping the address of the load balancer).
- Check the Advisor's log file for ERROR or WARNING messages and
take the appropriate corrective action. If you see an ERROR message
indicating a send() operation failed with "errno = EDC8102I Operation
would block" you might have too many groups or members registering
from the load balancer. Increase the TCPSENDBFRSIZE parameter of
the TCPCONFIG PROFILE.TCPIP statement, or register fewer groups and
members from the load balancer, and then try the operation again.
If ERROR and WARNING level log messages are not enabled, enable them,
repeat the operation, and recheck the log file again. Tip: Keep in mind that the Advisor has an internal maximum message size of 128K bytes. If this limit is exceeded, the connection is closed and an error message is logged stating that the message is too large and was not received.
- Check the load balancer for errors.