Troubleshooting Siebel Native Load Balancing

This topic provides guidelines for resolving problems with Siebel native load balancing. To resolve a problem, look for it in the list of symptoms or error messages in the following table. Some problem solutions in the table require changing the function of server components.

Problem	Cause	Solution
Users do not get a login page. The browser might display Server Busy Error.	Verify TCP port access for Siebel Servers, Siebel Gateway, and Siebel Application Interface.	See Verifying Load Balancing Port Access on Siebel Servers.
	Increase the Siebel Application Interface logging level.	To turn on detailed Siebel Application Interface logging, increase the log level for Siebel Application Interface. For more information, see the information about configuring the Siebel Application Interface in Siebel Installation Guide. The logs for this module are located in SIEBEL_AI_ROOT/applicationcontainer_external/logs.
Users can connect but loads are not balanced evenly between Siebel Servers	Unequal loads might be caused by characteristics of users and jobs.	Because jobs are distributed in a round-robin fashion, it is normal for a snapshot of the servers to show somewhat unequal loads. Unequal loads can be caused by several things, including the nature of the jobs and the rate at which users log in and log out on different servers. Over a longer period, the number of sessions handled by each server evens out.
	Siebel Servers do not have equal access to computing resources.	Verify that all of the Siebel Servers have equal access to computing resources such as CPU and memory.
	A Siebel Server has recently been added or has been restarted.	Load balancing is based on user logins. During the process in which current sessions are terminated and new sessions are started, the new Siebel Server is included in the load sharing.
	A Siebel Application Interface cannot route requests to one or more Siebel Servers.	Check for connectivity problems between the Siebel Application Interface and the Siebel Server with the low workload, as described earlier in this table.
	A Siebel Server is rejecting an unusual number of user requests.	Check the Siebel Application Interface log files for SISNAPI Connection Refused messages. Possible causes are: The SCBroker component either is not running or is listening on a different port. The requested Application Object Manager is not running or cannot run any more tasks. The requested Application Object Manager has a task or thread that is not responding. The Application Object Manager cannot communicate with the database server.
	A Siebel Server has functional or configuration problems.	Enable server diagnostics. Look for problems with components. Verify that the basic configuration is correct. For more information about monitoring and diagnosing server problems, see Siebel System Monitoring and Diagnostics Guide.