Resolution:
Description:
===========
Misconfigured WKA or busy cluster exception encountered during startup of TIBCO BusinessEvents cache servers.

Environment:
===========
TIBCO BusinessEvents 4.x
All Operating Systems
Coherence Cache

Symptoms :
===========
The following log entry indicates possible symptoms .

This Member(Id=0, Timestamp=2011-08-24 09:34:42.556, Address=6.6.6.5:8088, MachineId=1541, Location=machine:localhost,process:7602268, Role=SomeServer) has been attempting to join the cluster using WKA list [/192.167.0.1:9088, /192.167.0.2:9089] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.


Cause :
===========
The issue can be caused by any of the two reasons mentioned below:

1).The value for the hostname is invalid when setting tangosol.coherence.wka1 or tangosol.coherence.wka2 or both. For example, the issue could be that when configuring Coherence for the Cluster, identification names or hostnames provided are server1 or machine1 when hostname is server1.company.com or vice versa.

2).Several network interfaces are available causing Coherence to automatically select one of what is available rather than the configured address and port. This can be verified by observing IP addresses used for both Coherence nodes at runtime and verify if these addresses are different from those that are configured WKA list inside the BusinessEvents CDD file.

For example:
This Member(Id=0, Timestamp=2011-08-24 09:34:42.556, Address=6.6.6.5:8088, MachineId=1541, Location=machine:localhost,process:7602268, Role=WeblogicServer) has been attempting to join the cluster using WKA list [/192.167.0.1:9088, /192.167.0.2:9089] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.

In this case you may notice Address=6.6.6.5:8088 is different from elements of WKA list [/192.167.0.1:9088, /192.167.0.2:9089].


Resolution:
===========
For the first case mentioned, identify the correct hostname of the physical server(s) used for installation. Use the IP address or the output of the hostname command in Windows and Unix machines to ensure that you are using the correct identification names of the servers.

In the second case, using local address and localport may solve the issue. For example, if you have two machines they can be configured with well known addreses as shown below in the CDD .

tangosol.coherence.wka1=192.167.0.1
tangosol.coherence.wka1.port=9088
tangosol.coherence.wka2=192.167.0.2
tangosol.coherence.wka2.port=9089
tangosol.coherence.localhost=192.167.0.1
tangosol.coherence.localport.adjust=false
tangosol.coherence.localport=9088