Kbase 21607: Possible reasons why a broker may fail to register to the NameServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/04/2010 |
|
Status: Verified
SYMPTOM(s):
Errors 8552 in the AppServer broker log file.
The NameServer indicated that it failed to register the broker. (8552)
Error 8221 in the NameServer log file.
Erroneous UUID <UUID> received from Broker <Name> <Host> <Port>. UUID already registered by Broker <Name> <Host> <Port>. (8221)
FACT(s) (Environment):
OpenEdge Server Technology Category: AppServer
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
These error messages may be displayed under the following conditions;
1) The UUID (Universal Unique Identifier) is not unique within
the ubroker.properties file, thus the value for the broker is
identical to an existing entry (possibly another broker)
within the file.
This can occur when a user copies an existing entry into the new
entry. For example, within the ubroker.properties file, wsbroker1
exists with UUID of XXYYZZ. When a second broker is added manually,
it contains the same properties as wsbroker1, thus including the same
UUID value. Please note that these types of issues rarely occur on
Windows a environment since the UUID value is created automatically via the Progress Explorer.
2) The UUID is invalid.
This can occur if the user copies an existing ubroker.properties file
from machine A to machine B. Since the broker(s) identified within
the ubroker.properties file contain IP information of machine
A (along with other information), when running the file on another machine or even a machine which has a different network, the broker(s) may startup fine, but fail to register to NameServer.
3) AppServer broker running unmanaged and listening on different port
This can occur if the previous shutdown of the AppServer broker did not complete
successfully and the broker process remained running unmanaged by the AdminServer.
AppServer broker listening port was changed and then the new broker instance was started.
As the broker now listens on different port number it started, but it failed to register
with the NameServer as the previous one (now running unmanaged) is still registered.
Fix is to determine the unmanaged broker process pid and then to kill it using the
operating system command.
FIX:
In these types of situations, simply regenerate a new UUID via the GENUUID utility. Stop the broker, copy the id to the broker's UUID property attribute, save the changes and restart the broker(s).