Kbase P108880: NameServer reports broker as registered even though it has been stopped
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/09/2005 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
WebSpeed 3.x
SYMPTOM(s):
NameServer reports broker as registered even though it has been stopped
Broker shutdown executed using Progress Explorer or command prompt utilities such as wtbman, asbman
Using nsman -q reports broker as registered with the NameServer
CAUSE:
This is expected behavior. Broker shutdown command line utility connects
to the AdminServer and sends broker shutdown message after which it terminates
and returns to the command prompt.
FIX:
The issue where it can be seen that the broker is still registered with the NameServer
even though the shutdown has been executed, is because the 'wtbman' command spawns
additional java process which using the RMI sends the shutdown command to the AdminServer
and then returns back to the prompt.
However, as some agents might still be in the BUSY state, WebSpeed (or AppServer) broker
needs to wait for them to revert back to the AVAILABLE state before it shuts them down.
As this might take certain amount of time, broker will still be registered with the NameServer.
Once it shuts down all of the agent processes, it will notify the NameServer with the
UDP message that it goes down. After that NameServer will unregister the broker.
Even if it would happen that broker doesn't send that message, but it goes down for
whatever reason, NameServer would detect that there are no more keep-alive broker messages
and it would unregister it itself. Broker's NameServer keep-alive period is also configurable parameter
named 'Registration retry' in the Progress Explorer broker's advanced properties, or registrationRetry
within ubroker.properties file and its defaults is 30 seconds.