Kbase P136660: WebSpeed messenger doesn't connect to non-default NameServer port.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/30/2008 |
|
Status: Unverified
SYMPTOM(s):
WebSpeed messenger doesn't connect to non-default NameServer port.
WebSpeed messenger log file (msngr.log) shows the messenger trying to connect to port 5162 or a bogus port number.
WebSpeed messenger log file shows the messenger trying to connect to a negative port number.
Name Server at <host> Port 5162 is not responsive. (8239)
Name Server at Host <host> Port -16374 is not responsive. (8239)
WebSpeed messenger is trying to connect to the default NameServer port.
Msngr: the specified service name does not exist or has a bad format. (5825)
"vi ubroker.properties" on UNIX shows ^M characters at the end of each line.
"file ubroker.properties" on Linux says "ASCII English text, with CRLF line terminators".
FACT(s) (Environment):
WebSpeed messenger's ubroker.properties file NameServer entry has been changed to use a non-standard port.
UNIX
Linux
WebSpeed
CAUSE:
The ubroker.properties file has been transferred from a Windows based operating system to UNIX / Linux and contains Carriage Return characters. These characters are causing the properties file to be read incorrectly, triggering the messenger to default to port 5162.
FIX:
Run a utility such as dos2unix if it's available on the operating system being run. This utility strips the DOS characters from the file.
Alternatively, use ftp to transfer the file from Windows to UNIX using ASCII (not binary). This mode will also strip the DOS characters from text files.