OpenEdge Management and OpenEdge Explorer: Configuration

Advanced Features
Oracle DataServer configuration and administration
Table 3–5: Oracle DataServer broker properties (4 of 4)
Property Description
Maximum client instances The maximum number of client connections
that the broker can support concurrently.
The default value of 512 that is set for this
parameter is high enough to ensure that the
number of client connections is unlimited.
Realistically, however, the system-level
resources needed to support an unlimited
number of clients might be exhausted before
this limit is reached. If you see broker log
entries that contain Exception Messages for
"out of space" or "OutOfMemory" you might
need to reduce the maximum number of client
connections to a more reasonable value. Note,
however, that lowering this value can cause
some client requests to be rejected ("Exceeded
Max Clients"). Configuring and starting
multiple brokers to handle higher client loads
alleviates the problem.
Priority weight (0-100)
(dynamic property)
An integer value between 0 and 100 that
influences the share of the workload that the
selected broker receives. The larger the value,
the heavier the load that is distributed to the
broker. Using the Priority weight value, the
NameServer distributes client requests to the
same DataServer service across all DataServer
brokers. The default value is 0.
You can update this property dynamically.
Any changes will affect all current and new
brokers.
Registration retry (in seconds) After registering with its controlling
NameServer, the DataServer broker
periodically sends "keep-alive" messages to
the NameServer to let the NameServer know
that the broker is still active. The Registration
retry value is the number of seconds that pass
between "keep-alive" messages. The default
value is 30.
3–19