OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuring SonicMQ Adapters<br />
8–8<br />
Table 8–5: SonicMQ Adapter Broker Logging Setting properties (2 of 2)<br />
Property Description<br />
Broker log file threshold size A limit on how large the log file can get (in<br />
bytes). When the log is full, the broker creates<br />
a new log file with a sequence number (1 to<br />
999,999).<br />
Possible values: 500000 - 2147483647.<br />
Maximum number of broker log<br />
files<br />
A limit on how many broker log files are kept<br />
on the system when there is a threshold limit.<br />
The value represents the number of log files<br />
including the current one. Includes any rolled<br />
over log files that already exist when process<br />
started.<br />
Table 8–6: SonicMQ Adapter Broker Advanced Features properties<br />
(1 of 2)<br />
Property Description<br />
Maximum client instances The maximum number of client connections<br />
the SonicMQ Adapter broker can support<br />
concurrently. The default value 512 is high<br />
enough to ensure that the number of client<br />
connections is unlimited. Realistically,<br />
however, the system-level resources required<br />
to support an unlimited number of clients<br />
might be exhausted before this limit is<br />
reached. If you see broker log entries that<br />
contain Exception Messages for out of space<br />
or out of memory you might need to reduce<br />
the maximum number of client connections to<br />
a more reasonable value. Note that lowering<br />
this value can cause some client requests to be<br />
rejected (Exceeded Max Clients). Configuring<br />
<strong>and</strong> starting multiple brokers to h<strong>and</strong>le higher<br />
client loads will alleviate the problem.<br />
Priority weight<br />
(dynamic property)<br />
Defines a load-balancing priority for this<br />
broker relative to other brokers.<br />
You can update this property dynamically.<br />
Any changes will affect all current <strong>and</strong> new<br />
brokers.<br />
Registration retry The number of seconds that pass between<br />
broker keep-alive messages. After registering<br />
with its controlling NameServer, the<br />
SonicMQ Adapter broker periodically sends<br />
keep-alive messages to the NameServer to let<br />
the NameServer know that the broker is still<br />
active. (The default is 30.)<br />
TCP/IP version The TCP/IP version.
Change language