Troubleshooting Content Based Routing

Use the information that is provided to help you solve problems that can occur in Content Based Routing.

Click a link in the table to go to a full description and possible solution for the problem that you are experiencing.
Table 1. CBR Troubleshooting table
Symptom Possible cause Got to...
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.  


Terms and conditions for information centers | Feedback

Last updated: January 30, 2013 03:00 PM EST
File name: ttrb_cbr.html