Kbase P76291: Does unified brokers bound to specific network interface when working in a multiple NIC environment?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/10/2009 |
|
Status: Verified
GOAL:
Does unified brokers bound to specific network interface when working in a multiple NIC environment?
GOAL:
How to force unified broker to register with specific IP/Hostname?
GOAL:
How does admin server IP/Hostname affect unified brokers?
FACT(s) (Environment):
Progress 9.x
WebSpeed 2.x
All Supported Operating Systems
OpenEdge 10.x
WebSpeed 3.x
FIX:
When the WebSpeed / Appserver / unified broker starts it is not bound to a specific IP address, but instead it listens on all interfaces. The registrationMode=Register-IP or registrationMode=Register-HostName
in the ubroker.properties section for that broker determines the host name or ip address that broker will use to register to the NameServer. That does not mean that the broker is bound to the specific IP address.
When the AppServer broker is started up, it listens for the specified port on all interfaces. There is currently no option for the broker to tell it to listen on a particular interface.
Setting the -Djava.rmi.server.hostname property forces the AdminServer's RMI to return the specific hostname (or ip address) and as a side effect it will cause that the broker started from that AdminServer will choose the same hostname/ip address.
For example, you could use -Djava.rmi.server.hostname=host1 for
the AdminServer and yet specify:
registrationMode=Register-HostName
hostName=host2
and end up with AdminServer bound to one ip address and WebSpeed broker to another one.