CustomWare
 
 

when configuring a Broker territory / gateway across a firewall, you may come across the following error in your Broker Logs in WmBrokerAdmin:

2008-07-23 18:42:51 EST 1172 - Broker "Broker65 #1": Cannot connect to
Broker Server "xxx.xxx", error in resolving hostname to IP
address: Not owner.

Where xxx.xxx is the hostname on the OTHER side of the firewall.

Ensure that locally, you can resolve xxx, and xxx.xxx from the unix/operating system level. Do this on both sides of the firewall on both Broker machines.

Once it works, your broker documents will sync and connections should stay. setting a keep alive to a large value, such as 600 seconds (10 minutes) will ensure that overnight and during quiet periods that the connection is maintained if you have aggressive firewall settings.

The log message once connected should look like this:

2008-07-24 07:59:36 EST 1187 - Broker "Broker65 #1": A broker
connection to "Broker65 #1"@xxx.xxx:7811 was successfully
established.

There is also a parameter in awbroker.cfg you can use ("hostname=<ip address>"), but I recommend getting things working at the operating system level.
See Also http://advantage.webmethods.com/article/?id=SR-1-59436161