Use the information that is provided to help you solve problems that can occur in Site Selector.
Symptom | Possible cause |
---|---|
Site Selector not running correctly | Conflicting port number |
Site Selector does not round-robin incoming requests from Solaris client | Solaris systems run a "name service cache daemon" |
The sscontrol or lbadmin command fails with ‘Server not responding' or ‘unable to access RMI server' message | Commands fail due to socksified stack. Or commands fail due to not starting ssserver. |
ssserver fails to start on Windows platform | Windows systems do not require the host name to be in the DNS. |
Machine with duplicate routes not load balancing correctly - name resolution appears to fail | Site Selector machine with multiple adapters attached to the same subnet |
Unexpected GUI behavior when using Windows platform paired with Matrox AGP video card | Problem occurs when using Matrox AGP video cards while running the Load Balancer GUI |
GUI hangs (or unexpected behavior) when trying to load a large configuration file. | Java does not have access to enough memory to handle such a large change to the GUI |
On Windows platform, corrupted Latin-1 national characters appear in command prompt | Change font properties of command prompt window |
On HP-UX platform, the following message occurs: java.lang.OutOfMemoryError unable to create new native thread | Some HP-UX installations by default allow 64 threads per process. This is insufficient. |
On Windows platform, advisors and reach targets mark all servers down | Task offloading is not disabled or may need to enable icmp. |
On Solaris systems, Load Balancer processes end when you exit the terminal session window from which they started | Use the nohup command to prevent the processes that you started from receiving a hangup signal when you exit the terminal session. |
This problem can occur when another application is using one of the ports used by Site Selector. For more information, go to Checking Site Selector port numbers.
Symptom: Site Selector component does not round-robin incoming requests from Solaris clients.
Possible cause: Solaris systems run a name service cache daemon. If this daemon is running, the subsequent resolver request is answered from this cache instead of querying Site Selector.
Solution: Turn off the name service cache daemon on the Solaris machine.
EXCLUDE-MODULE java
EXCLUDE-MODULE javaw
This can cause problems when one of the administration consoles runs on the same machine as a firewall or through a firewall. For example, when Load Balancer runs on the same machine as a firewall, and you issue sscontrol commands, you might see errors such as Error: Server not responding.
To avoid this problem, edit the ssserver script file to set the port used by RMI for the firewall (or other application). Change the line: LB_RMISERVERPORT=10199 to LB_RMISERVERPORT=yourPort. Where yourPort is a different port.
When complete, restart ssserver and open traffic for ports 12099, 10004, 12199, and 12100, or for the chosen port for the host address from which the administration console will run.
Site Selector must be able to participate in a DNS. All the machines involved in the configuration should also be participants of this system. Windows systems do not always require the configured host name to be in the DNS. Site Selector requires that its host name be define in the DNS to start properly.
Verify this host is defined in the DNS. Edit the ssserver.cmd file and remove the w from javaw. This change should provide more information about errors.
The Site Selector name server does not bind to any one address on the machine. It will respond to requests destined for any valid IP on the machine. Site Selector relies on the operating system to route the response back to the client. If the Site Selector machine has multiple adapters and any number of them are attached to the same subnet, it is possible the O/S will send the response to the client from a different address than it was received. Some client applications will not accept a response received from an address other than where it was sent. As a result, the name resolution will appear to fail.
On Windows platform when using a Matrox AGP card, unexpected behavior can occur in the Load Balancer GUI. When clicking the mouse, a block of space slightly larger than the mouse pointer can become corrupted causing possible highlighting reversal or images to shift out of place on the screen. Older Matrox cards have not shown this behavior. There is no known fix when using Matrox AGP cards.
Some HP-UX 11i installations are pre-configured to allow only 64 threads per process. However, some Load Balancer configurations require more than this amount. For HP-UX systems, set the threads per process to at least 256. To increase this value, use the sam utility to set the max_thread_proc kernel parameter. If heavy use is expected, you might need to increase max_thread_proc beyond 256.
To increase max_thread_proc, refer to the steps to increase the max_thread_proc parameter.
Refer to the section on disabling task offloading for instructions on configuring this setting.