Setting Up Threshold Detection for Load Balancing Requests from RMI-based Clients
When a request from an RMI-based client (such as an applet or another Java RMI-based client) is made on a method server, the current server checks to determine if any of the following thresholds have been surpassed.
|
Threshold
|
Description
|
|
wt.method.loadbalance.RMISockets
|
Defines the number of RMI sockets the server allows to be active before a ServerLoadException is thrown. Default is 0.
|
|
wt.method.loadbalance.activeContext
|
Defines the maximum number of currently active contexts allowed within the server before a ServerLoadException is thrown. Default is wt.pom.maxDbConnections.
|
If a threshold is surpassed, the server throws an exception using wt.method.ServerLoadExceptions which has a reference to the next server. The RMI client catches the exception and can then redirect its request to the server that is referenced.
The following property specifies the maximum number of times a single method call can be redirected:
wt.method.loadbalance.maxRedirects
The default setting is 1. A setting of 0 causes method calls to be redirected until a server that falls below the thresholds is identified.
If a threshold is set to zero, or is not defined within wt.properties, the threshold is ignored.