Business Event (BE) engine 4.0 with Cache type OM (ObjectManager) gives error message; "[runtime.service] Initializing Coherence failed java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)".

Business Event (BE) engine 4.0 with Cache type OM (ObjectManager) gives error message; "[runtime.service] Initializing Coherence failed java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)".

book

Article ID: KB0086300

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Description:
BE engine may start on Windows on other platforms but then fail on another platform with the error message of 'Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)'.

Symptoms:
See error message in the "'Description".

Cause:
Check to see if there is an existing Business Events application running in the same environment with the same cluster properties. If so, change the values described in the "Resolution Section".

Issue/Introduction

Business Event (BE) engine 4.0 with Cache type OM (ObjectManager) gives error message; "[runtime.service] Initializing Coherence failed java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)".

Resolution

Change following in the cdd file:

         <cdd:property name="tangosol.coherence.clusteraddress" value="224.3.3.1"/>
            <cdd:property name="tangosol.coherence.clusterport" value="31337"/>

The values used are decided by the user.

Attachments:
==========
See the attached document (Filename:P "FullStack.txt:) for full stack.

Attachments

ka11a000000HqpcAAC get_app