How can I get my RTclient to connect to RTserver in a clustered environment?
Article ID: KB0089557
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
Problem: RTclient will not connect to RTserver using a virtual IP in its server_names list but will work fine if the true IP address is used.
Solution: On *all* machines in the cluster where the RTservers are running define the following undocumented environment variable before connecting the clients:
$ setenv RT_FORCE_NODE_NAME <to the 'cluster name' or cluster IP>
Without this environment variuable set what is happening is that the client is requesting a conn using the cluster name (or IP) but during the server handshake the server is returning the physical node name which doesn't match the request. By setting this environment variable on the machine where the RTserver will run the RTserver will instead return the cluster name (or IP) in the handshake which will allow the client to complete the connection.
Problem: RTclient will not connect to RTserver using a virtual IP in its server_names list but will work fine if the true IP address is used.
Solution: On *all* machines in the cluster where the RTservers are running define the following undocumented environment variable before connecting the clients:
$ setenv RT_FORCE_NODE_NAME <to the 'cluster name' or cluster IP>
Without this environment variuable set what is happening is that the client is requesting a conn using the cluster name (or IP) but during the server handshake the server is returning the physical node name which doesn't match the request. By setting this environment variable on the machine where the RTserver will run the RTserver will instead return the cluster name (or IP) in the handshake which will allow the client to complete the connection.
Issue/Introduction
How can I get my RTclient to connect to RTserver in a clustered environment?
Feedback
Yes
No
Powered by
