Kbase P136394: How to tell if a secondary login broker has started for database connections ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/19/2009 |
|
Status: Verified
GOAL:
how do I see secondary login broker from promon?
GOAL:
How to verify that a secondary broker is running?
GOAL:
How to tell if a secondary login broker has started for database connections ?
GOAL:
How can I tell if multiple database login brokers have started?
GOAL:
How can i tell how many secondary login database brokers have started?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
There are 3 methods to find out if multiple login brokers have started against a database.
METHOD 1:
Parse the database log file for message:
"BROKER 1: (5645) This is an additional broker for this protocol."
Further detail about this secondary login broker can be obtained from the pre-ceeding message:
BROKER 1: (5644) Started for 9667 using TCP, pid 2500.
In OpenEdge 10.1C this message has been further enhanced:
BROKER 1: (5644) Started for 9666 using TCP IPV4 address 0.0.0.0, pid 3208.
Note: The "BROKER number will be any number except zero, which is reserved for the initial login broker when the database is first started, ie "BROKER 0:" The number increments depending on how many secondary login brokers have been started with the -m3 parameter and which -Mn slot was available when they were started.
METHOD 2:
View the Server's status in "promon dbname > R&D > option 1. Status Displays > 3. Servers.
All entries with TYPE = Login are login brokers.
TYPE = Auto are the remote servers spawned by the login brokers.
At the time of writting, it is not possible to differentiate in promon which remote servers are spawned by which login broker - other than to maintain distinct "-minport -maxport" ranges in the login broker startup parameters.
Example:
10/30/08 Status: Servers
11:14:32
Sv Pend. Cur. Max. Port
No Pid Type Protocol Logins Users Users Users Num
0 2352 Login TCP 1 0 0 7 9556 << -minport 10100 -maxport 10120
1 2500 Login TCP 1 0 0 5 9667 << -minport 10200 -maxport 10220
2 1524 Auto TCP 1 0 0 7 10100
3 2964 Auto TCP 1 0 0 5 10200
4 0 Inactive 0 0 0 0 0
METHOD 3:
Use the _SERVERS Virtual System Tables (VST) to query the current status:
EXAMPLE:
FOR EACH _Servers
WHERE _Servers._Server-Type <> "Inactive"
BY _Servers._Server-PortNum:
DISPLAY
_Server-Num LABEL "SVR_num"
_Server-Type LABEL " Server type"
_Server-Pid LABEL " PIDsvr"
_Server-PortNum LABEL " PORT#"
WITH 2 COL.
END.