SITA | NGHR2 Program Coherence Details for Deployment

Page 1 of 2

Confidential. Copyright SITA Information Networking Computing UK Limited 2009. All rights reserved
Coherence IP/PORT Update Details

Section 1: Coherence IP/PORT Details

We need to use different IP ADDRESS and PORT for different cluster-names in coherence configuration files in an environment and
the IP/PORT must be unique across different environments (like FAT1, FAT4, UTL2, sns-admin).

Please refer to below table to update coherence configuration while deploying applications in different environments.

To avoid coherence issues we MUST FOLLOW it.



Coherence Details for Deployment
(CDS-LD, CDS-LD-CACHE, CDS-RD, CJ, CJM, SIAM)
Environment
Cluster: CDS-Cluster
(cds-ld, ld-cache, rd-cache,
cjm)
Cluster: CDS-2.0, CDS-3.0
(cds-rd-2, cds-rd-3)
Cluster: CJ9.0Cluster
(cj)
Cluster: SM1.2Cluster
(siam)
IP PORT IP PORT IP PORT IP PORT
FAT1 231.0.0.133 21765 231.0.0.132 21665 231.0.1.231 21365 231.0.0.131 21565
UTL2 232.0.0.133 22765 232.0.0.132 22665 232.0.1.231 22365 232.0.0.131 22565
SNS-ADMIN 233.0.0.133 23765 233.0.0.132 23665 233.0.1.231 23365 233.0.0.131 23565
FAT4 234.0.0.133 24765 234.0.0.132 24665 234.0.1.231 24365 234.0.0.131 24565

Pattern followed is:
#1. For IP address - update first 3 digits as (FAT1: 231, UTL2: 232, SNS-ADMIN: 233, FAT4: 234)
#2. For PORT - update first 2 digits as (FAT1: 21, UTL2: 22, SNS-ADMIN: 23, FAT4: 24)

SITA | NGHR2 Program Coherence Details for Deployment

Page 2 of 2

Confidential. Copyright SITA Information Networking Computing UK Limited 2009. All rights reserved
Section 2: Coherence Issue/Solution

If we deploy applications (having coherence configuration) in multiple environments/servers with default IP and PORT, we may encounter the coherence related
issues in which different managed servers join the same coherence-cluster across the environments.

Please see the log below in which FAT1 and FAT4 servers have joined the coherence cluster and throwing tangosol exception:

Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=2, Name=CDSCACHE, Type=DistributedCache
MemberSet=ServiceMemberSet( OldestMember=
Member(Id=11, Timestamp=2014-01-14 10:10:22.006, Address=172.17.187.154:8098, MachineId=51331, Location=site:,machine:ss-fat1-wls2,process:17042,
Role=WeblogicServer) ActualMemberSet=MemberSet(Size=5
Member(Id=10, Timestamp=2014-01-15 10:33:56.884, Address=172.17.187.239:8090, MachineId=7136, Location=site:,machine:ss-fat4-wls2,process:4120,
Role=WeblogicServer)
Member(Id=11, Timestamp=2014-01-14 10:10:22.006, Address=172.17.187.154:8098, MachineId=51331, Location=site:,machine:ss-fat1-wls2,process:17042,
Role=WeblogicServer)
Member(Id=12, Timestamp=2014-01-15 10:34:26.32, Address=172.17.187.238:8090, MachineId=1119, Location=site:,machine:ss-fat4-wls1,process:3974,
Role=WeblogicServer)
Member(Id=15, Timestamp=2014-01-14 10:27:31.169, Address=172.17.187.157:8112, MachineId=45314, Location=site:,machine:ss-fat1-wls1,process:7268,
Role=WeblogicServer)
Member(Id=16, Timestamp=2014-01-14 10:27:32.046, Address=172.17.187.154:8112, MachineId=51331, Location=site:,machine:ss-fat1-wls2,process:17042,
Role=WeblogicServer) )

To avoid coherence related issues, we need to update the IP/PORT as per the table given in Section 1.