Kbase P33300: WebSpeed messenger cannot see any information for new broker when registerNameServer=0
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/11/2004 |
|
Status: Unverified
FACT(s) (Environment):
WebSpeed 3.1x
SYMPTOM(s):
WebSpeed messenger cannot see any information for new broker, wsbroker2
Messenger does not communicate with second broker, wsbroker2
No information is seen when using URL http://localhost/scripts/cgiip.exe/WService=wsbroker2/workshop
Messenger is configured to talk to older broker, wsbroker1
Messegner bypasses NameServer and talks directly to 1 broker, wsbroker1
Messenger has registerNameServer=0 set and using port of wsbroker1
Can use the NameServer
CHANGE:
A second WebSpeed broker (wsbroker2) is added to the ubroker.properties file
CAUSE:
Since the Messenger is configured to bypass the NameServer and talk directly to the first broker, wsbroker1, it will not communicate with any other broker.
FIX:
If you're open to using the NameServer, then you have more freedom and flexibility in fixing this issue. Using the NameServer allows the messenger to go through the NameServer and all brokers that are registerd with it, do the following:
1. change the registerNameServer=1
2. change the port to the port of the NameServer
3. Add attribute controllingNameServer= and set it to the NameServer name
Example
[WebSpeed.Messengers.CGIIP]
msngrExecFile=@{Startup\DLC}\bin\cgiip.exe
controllingNameServer=NS1
msngrScriptFile=
registerNameServer=1
Port=5162