Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | - |
Not Applicable | - |
Resolution:
Description:
===========
Unicast Configuration using TCP for Active Spaces.
Environment:
===========
All Operating Systems
TIBCO BusinessEvents 5
Root Cause:
===========
By default Active Spaces configuration uses the tibpgm protocol .
Resolution:
===========
In this setting there are two machines , machine 1(M1) and machine 2(M2) . Cache-agent started on M1 and Inference-agent started on M2 .
IP address of machine(M1) - 10.105.70.20
IP address of machine(M2) - 10.105.72.36
Add these two properties with corresponding values in cluster level of the project CDD file .
Use the same port number with IP address in cache on M1
be.engine.cluster.as.discover.url=tcp://10.105.70.20:55000
be.engine.cluster.as.listen.url=tcp://10.105.70.20:55000
The logs will show this on cache console:
[2012-09-27 11:37:12:954][9212][1544][INFO][transport] ip_address=10.105.70.20 port=55000
[2012-09-27 11:37:17:963][9212][1544][INFO][fdcache.ms] Connected metaspace name=[fdcache], listen=[tcp://10.105.70.20:55000], discovery=[tcp://10.105.70.20:55000], member name=[a694614-d6d8] version=2.0.1.040
[2012-09-27 11:37:17:963][9212][12276][INFO][fdcache.$members] member joined: 10.105.70.20:55000
Verification :
Note: In the log trace look at the following line
listen=[tcp://10.105.70.20:55000], discovery=[tcp://10.105.70.20:55000] , [tcp] - indicates tcp is used
On the Inference-agent on M2 : only use cache discovery URL , do not add listen URL here. Add this property with corresponding values in cluster level of the project CDD file .
be.engine.cluster.as.discover.url=tcp://10.105.70.20:55000
The logs will show this on inference console:
[2012-09-27 11:37:40:463][14568][14976][INFO][transport] ip_address=10.105.72.36 port=50000
[2012-09-27 11:37:45:670][14568][15132][INFO][fdcache.$members] member joined: 10.105.70.20:55000
[2012-09-27 11:37:45:670][14568][14976][INFO][fdcache.ms] Connected metaspace name=[fdcache], listen=[tcp://10.105.72.36:50000], discovery=[tcp://10.105.70.20:55000], member name=[a694824-c350] version=2.0.1.040
[2012-09-27 11:37:45:670][14568][15132][INFO][fdcache.$members] member joined: 10.105.72.36:50000
Verification :
Note: In the log trace look at the following line:
listen=[tcp://10.105.72.36:50000], discovery=[tcp://10.105.70.20:55000] , [tcp] - indicates TCP is used