No Load Balancing When You Invoke Many APPC ConversationsLast reviewed: April 17, 1997Article ID: Q148618 |
The information in this article applies to:
SYMPTOMSLU6.2 load balancing problems have been observed under two conditions: 1) When a single program allocates multiple conversations: If an APPC or CPIC program allocates multiple conversations at the same time on an SNA Server client or server and SNA Server is configured to support LU6.2 load balancing, the conversations may not load evenly across more than one SNA Server. For example, if a program tries to allocate 16 concurrent conversations across two SNA Servers, which are configured to support 10 sessions each, the program may allocate 10 conversations through the first server and two conversations through the second server. The remaining four conversations are queued against the first server. 2) When multiple APPC or CPIC programs allocate conversations at once: For example, if multiple programs are started and each tries to allocate one conversation, where two SNA Servers are available, sessions tend to be allocated from only one SNA Server.
CAUSEThis problem occurs when the LU6.2 sessions are not activated before the application attempts to allocate the conversations. When an APPC or CPIC application allocates a conversation, the SNA Server APPC interface attempts to locate an appropriate, available LU6.2 session on any SNA Server running in the domain or subdomain. It selects a server that has an active LU6.2 session before it tries to select a server that has an inactive LU6.2 session. If multiple conversations are allocated at the same time by a program, the APPC interface does not randomly select between servers if they all start LU6.2 sessions. This can cause multiple conversation startup requests to be queued against a single SNA Server rather than load balancing across multiple SNA Servers.
RESOLUTIONTo work around this problem:
STATUSMicrosoft has confirmed this to be a problem in SNA Server 2.11 and SNA Server 2.11 Service Pack 1. This problem was corrected in the latest Microsoft SNA Server 2.11 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words: prodsna
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |