Kbase P176308: Errors 6019 and 5804 (with Error -66) occur when attempting to ping the webspeed broker in a distrib
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/28/2010 |
|
Status: Unverified
SYMPTOM(s):
Getting errors when attempting to ping the WebSpeed broker
WebSpeed error from messenger process (6019)
Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -66
Working within a Distributed Configuration
Connecting directly to the broker works fine
From WebServer, able to ping the WebSpeed Transaction Server using IP address
The same AIX server has 5 ip address with multiple WPAR (Workload Partition)
Nameserver status shows the different IP address from broker registration than intended
AdminServer is running on the IP that is not intended for WebSpeed broker
The AdminServer can not be run on the IP address of the WebSpeed broker as other AppServer broker needs to be on that IP address
FACT(s) (Environment):
IBM AIX 5.3
OpenEdge 10.x
WebSpeed 3.1x
CAUSE:
CGI messenger when going through the NameServer is getting the wrong IP address to connect to the broker, hence, the error 5804 with error -66.
FIX:
Run the AdminServer from non-default location per solution P94699 and use the intended IP and different port for AdminServer per solution P137292 . Make sure to change the NameServer port as well as another NameServer is running to service AppServer brokers. The broker registrationMode needs to be change to Register-Hostname and add hostname=<intended IP address the AdminServer is running on> under the broker section
On the messenger WPAR, change the NameServer host name to be the correct IP address and the port number it is running on.