Kbase P127864: SonicMQ Adapter broker does not register with NameServer for NameServer Load Balancing
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/05/2009 |
|
Status: Verified
SYMPTOM(s):
SonicMQ Adapter broker does not register to NameServer
Errors 8552 is present within SonicMQ Adapter broker log file
The NameServer indicated that it failed to register the broker. (8552)
Errors 8208 and 8210 are present within NameServer log file
Registration Failure: Load Balancing Not Available. Broker <UUID> Not Registered. Application Service <Application Service> already being used. (8208)
Unregistering Broker <Broker Name>. (8210)
New SonicMQ Adapter broker is added to the ubroker.properties file by copying information from existing broker for the new broker.
Multiple SonicMQ Adapter brokers have the same Application service name in their AppService Name List
Multiple SonicMQ Adapter brokers are running fine on system
All SonicMQ Adapter brokers except the new broker registers to NameServer
Name Server Load Balance license is not installed on system (progress.cfg shows no Name Server Load Balance bit)
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
There are two options:
Option 1:
To enable Name Server Load Balancing for multiple SonicMQ Adapter brokers, install the Name Server Load Balancing license. After installation, a Name Server Load Balance bit should be listed in the progress.cfg file. Contact the sales representative for information regarding how to obtain this license.
Option 2:
If the NameServer Load Balancing license is not installed on the system, then only one SonicMQ Adapter broker with a particular Application service name can register with the Name Server.
To disable a second SonicMQ Adapter broker from registering with the Name Server with the same Application service name as another broker through the Progress Explorer, follow these steps:
1) Click the properties of the second broker.
2) Expand the "Broker" section.
3) Highlight "AppService Name List".
4) Rename the Application service name that matches the Application service name of the another SonicMQ Adapter broker.
To disable a second SonicMQ Adapter broker from registering with the Name Server with the same Application service name as another broker by manually editing the ubroker.properties file, follow these steps:
1) Find the section where the SonicMQ Adapter is defined.
2) For the "appserviceNameList" value, rename the Application service name that matches the Application service name of the another SonicMQ Adapter broker.
3) Save the file and then restart the AppServer.
If the AdminServer is running when the file is edited, the AdminServer will restart once changes are saved.