The JMS flow collaborates
the communication between more than one ServiceMix JBI container instance. A
message queue is used for each JBI endpoint, so that multiple instances of the same
named component deployed in different instances of the ServiceMix in the cluster
have requests load balanced across them.
In a ServiceMix cluster, deployment happens in the same way as we do in a normal
ServiceMix JBI container (both for POJO and archive Component deployment) but
all ServiceMix container instances in the cluster are notified of a deployment. The
underlying JMS flow will handle automatic routing, load balancing, and failover of
MessageExchange(s) between the different ServiceMix containers instances in
the cluster.
In the cluster mode all ServiceMix instances participating in the cluster must have
a unique name in the whole cluster. Let us look into a sample configuration to
understand this well. In our hypothetical sample cluster, assume that we will have
three ServiceMix containers instances. As one of these ServiceMix instances also
manages a JMS connection broker, we will arbitrarily name that instance with the
name "admin".
Pages:
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493