| LoadBalancingPolicy implementation that always favor the first available target i.e.
no load balancing occurs. Nevertheless, the first target is randomly selected.
This does not mean that fail-over will not occur if the
first member in the list dies. In this case, fail-over will occur, and a new target
will become the first member and invocation will continously be invoked on the same
new target until its death. Each proxy using this policy will elect its own
prefered target: the target is not shared accross the proxy family (for this
behaviour please take a look at FirstAvailableIdenticalAllProxies)
author:
Bill Burke.
author:
Sacha Labourey.
version:
$Revision: 57188 $
See Also: org.jboss.ha.framework.interfaces.LoadBalancePolicy
See Also: Revisions:
See Also: 2002/08/24: Sacha Labourey
See Also:
See Also: - Use the target repository
See Also: - First choice is randomly selected to distribute the initial load
See Also: - When the list of targets change, we try to keep using the same
See Also: previously elected target node if it still exists. Previously,
See Also: we were working with the position id of the target node, thus
See Also: if the list order changed, we were switching to another node
See Also: while our prefered node was still up
See Also:
|
