J2EE development with Oracle products

mod_oc4j Load Balancing support follow routing strategies:

Random
route the request to next JVM in a cluster in usage of the randomm algorithm.

Random with local affinity
route the request to next JVM on the local machine in usage of the random algorithm, if none available
it reroute to the next remote JVM also in usage of the ramdom algorithm.

Random with routing weight
route each request randomly to all available JVM in a cluster depending of the
configured routing resource weight. A high value (integer) means more resources available.

Round robin
choose for each request the next JVM in a cluster.

Round robin with local affinity
prefer the for each request the next JVM on the locale mashine
other it will use the next remotely.

Round robin with routing weight
prefer the for each request the next JVM in a cluster depending of the
configured routing resource weight.


Metric based
choose the JVM based on OC4J metrics and his availability.

Metric based with local affinity
first choose the JVM based on locale OC4J metrics and his availability otherwise it will choose the JVM remotely.

See also ...