Use the information that is provided to help you solve problems that can occur in Content Based Routing.
Symptom | Possible cause |
---|---|
CBR not running correctly | Conflicting port numbers |
The cbrcontrol 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 cbrserver |
Requests are not being load balanced | Caching Proxy was started before the executor was started |
On Solaris, the cbrcontrol executor start command fails with ‘Error: Executor was not started.' message | Command fails because the system IPC defaults may need to be modified, or link to library is incorrect. |
URL rule does not work | Syntactical or configuration error |
Unexpected GUI behavior when using Windows systems 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 Windows platform, problem resolving IP address to host name when more than one address is configured to an adapter | The IP address you want as your hostname must appear first in the registry. |
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 CBR. For more information, go to Checking CBR port numbers.
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 cbrcontrol commands, you might see errors such as Error: Server not responding.
To avoid this problem, edit the cbrserver script file to set the port used by RMI for the firewall (or other application). Change the line: LB_RMISERVERPORT=11199 to LB_RMISERVERPORT=yourPort. Where yourPort is a different port.
When complete, restart cbrserver and open traffic for ports 11099, 10004, 11199, and 11100, or for the chosen port for the host address from which the administration console runs.
Caching Proxy and CBR have been started, but requests are not being load balanced. This error can occur if you start Caching Proxy before starting the executor. If this happens, the stderr log for Caching Proxy will contain the following error message: "ndServerInit: Could not attach to executor." To avoid this problem, start the executor before starting Caching Proxy.
On Solaris systems, the cbrcontrol executor start command returns: "Error: Executor was not started." This error occurs if you do not configure the IPC (Inter-process Communication) for the system so that the maximum size of a shared memory segment and semaphore IDs are bigger than the operating system's default. In order to increase the size of the shared memory segment and semaphore IDs, you must edit the /etc/system file. For more information on how to configure this file, see the section on modifying the system defaults for IPCs (Inter-process Communication).
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.
If you are using remote Web administration to configure Load Balancer, do not resize (Minimize, Maximize, Restore Down, and so on) the Netscape browser window in which the Load Balancer GUI appears. Because Netscape reloads a page every time browser windows are resized, this will cause a disconnect from host. You will need to reconnect to host each time you resize the window. If you are performing remote Web administration on a Windows platform, use Internet Explorer.
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.
On Windows platform, when configuring an adapter with more than one IP address, configure the IP address that you want affiliated to the host name first in the registry.
Because Load Balancer is dependent on InetAddress.getLocalHost() in many instances (for example, lbkeys create), multiple IP addresses aliased to a single adapter might cause problems. To avoid this problem, list the IP address to which you want your host name to resolve first in the registry.