Resolution:
Description:
===========
Why do TIBCO BusinessEvents cache/inference engines running on different servers not join the same cluster?

Environment:
==========
Operating Systems: ALL
TIBCO BusinessEvents Version: ALL

Symptoms:
=========
Cache/Inference engines running on two different servers with the same CDD(Cluster deployment descriptor) configured with multicasting  does not join the existing cluster.
This could cause each engine on both servers create a separate cluster of their own even if the servers are in the same subnet and the Coherence multicast test works fine.

Cause:
======
Machines (Servers) configured with multiple network cards and coherence unable to resolve localhost to a specific &ltIP Address>.

Resolution:
==========
Coherence could not resolve the localhost to a specific &ltIP Address> set for the property 'tangosol.coherence.localhost' on the CDD file. Change the value of the property 'tangosol.coherence.localhost' in the CDD file from 'localhost' to &ltIP Address> of the server where you are starting the be-engine(cache/inference).

Example:
If you are starting the be-engine cache on server10, make sure you have the &ltIP Address> of server10. Similarly on the other server, say server11, have the property 'tangosol.coherence.localhost' value set to &ltIP Address> of server11.

TIBCO BusinessEvents engines running on two different servers doesn't join the same cluster.