Multicast search for existing cluster nodes connects to engines on different virtual machines (VMWare) started on a local physical machine although thejava.property.tangosol.coherence.ttl is set to 0 .

Multicast search for existing cluster nodes connects to engines on different virtual machines (VMWare) started on a local physical machine although thejava.property.tangosol.coherence.ttl is set to 0 .

book

Article ID: KB0085128

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
===========
Multicast search for existing cluster nodes connects to engines on different virtual machines (VMWare) started on a local physical machine although the java.property.tangosol.coherence.ttl is set to 0 .

Environment:
===========
BusinessEvents 3.0.1/4.0.1
All Operating Systems

Symptoms:
=========
On startup the agent joins the cluster of another virtual machine when using the same cluster settings for both applications although tangosol.coherence.ttl was set to 0 .

Startup error when BusinessEvents applications are different:
"java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_ANNOUNCE)"

Cause:
======
The agent will search on all virtual machines for existing cluster nodes started on a single physical machine although the property java.property.tangosol.coherence.ttl=0 .

Resolution:
========
Two options:

1). Use unique cluster settings for each application on each virtual machine
(properties tangosol.coherence.cluster, tangosol.coherence.clusteraddress, tangosol.coherence.clusterport) .

2). Use internal IP 127.0.0.1 for property tangosol.coherence.localhost .

BusinessEvents 4.0.1:
add/change CDD  property "tangosol.coherence.localhost=127.0.0.1" (cluster area)

BusinessEvents 3.0.1:
add/change property "java.property.tangosol.coherence.localhost=127.0.0.1" to TRA file

Issue/Introduction

Multicast search for existing cluster nodes connects to engines on different virtual machines (VMWare) started on a local physical machine although thejava.property.tangosol.coherence.ttl is set to 0 .