Consultor Eletrônico



Kbase P60792: Errors 8552, 8208, & 8210 occur when defaultService=1 for multiple brokers
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   16/10/2008
Status: Verified

FACT(s) (Environment):

Progress 9.1x
WebSpeed 3.1x

SYMPTOM(s):

Broker does not register to NameServer

Errors 8552 is present within 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)

Multiple Brokers are running fine on system

All brokers except the new broker registers to NameServer

Name Server Load Balance license is not installed on system

Multiple brokers have defaultService=1 set or have "Support default service" enabled

CHANGE:

New broker is added to the ubroker.properties file. Information was copied from existing broker for the new broker

CAUSE:

There are mulitiple brokers that support default services when NameServer Load Balancing license is not installed on the system. When the broker registers with a NameServer, it indicates whether it supports the default application service, in addition to any listed in the appserviceNameList. Because the Load Balancing product is not installed, the second broker fails to register.

Example of the broker
Existing Broker:

[UBroker.WS.wsbroker1]
appserviceNameList=progress
autoStart=0
autoTrimTimeout=600
brokerLogFile=$WRKDIR/wsbroker1.broker.log
brkrLoggingLevel=4
controllingNameServer=NS1
defaultService=1 ---------------------------------------->Value set to 1

New Broker added:

[UBroker.WS.wsbroker2]
appserviceNameList=progress
autoStart=0
autoTrimTimeout=600
brokerLogFile=$WRKDIR/wsbroker2.broker.log
brkrLoggingLevel=4
controllingNameServer=NS1
defaultService=1 ---------------------------------------->Value set to 1

FIX:

You have two options.

Option 1:
If you do not have NameServer Load Balancing License, then you can only enable one broker to support the default service.

To disable the default services through the Progress Explorer, follow these steps:
1) Click the properties of the secondary broker.

2) Expand the "Broker" section.

3) Highlight "AppService Name List".

4) Uncheck "Supports default service".

To disable the default services by manually editing the ubroker.properties file, follow these steps:
1) Find the section where the AppServer is defined.

2) Set "defaultService" to equal 0 (zero).

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.

Option 2:
If you wish to enable "Support default services" or defaultService=1 for multiple brokers, then you must obtain the correct license that supports this feature. Install NameServer Load Balancing license. Contact your sales representative on how to obtain this license.