Kbase P60241: Getting 'Messenger directly connected to WebSpeed Transaction Server at Host:' when the messenger is
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 3.x
IIS
SYMPTOM(s):
Getting different information when performing Messenger-NameServer verify
Messenger directly connected to WebSpeed Transaction Server at Host: <hostname> Port: <1234>
Messenger is configured to use NameServer
Using wsisa.dll
wsisa.dll was originally connected directly to broker
CHANGE:
Configured WSISA to talk to the NameServer, rather than use the wsbroker directly
CAUSE:
After the changes are made in ubroker.properties file, the webserver is not stopped and restarted.
When making a change to the messenger ubroker.properties file (or even through the Progress Exp), you need to physical stop and restart the webserver for the changes to be in effect. This is because the messenger being used is a .dll, thus it is loaded into memory only when the webserver is started.
FIX:
Go into the "services" under Control Panel
1. Stop, "IIS Admin Service"
2. Restart the "World Wide Web Publishing Service"