In BusinessEvents 4.0.1, RequestTimeoutException is thrown when Well Known Addresses(WKAs) are used for starting cluster nodes.

book

Article ID: KB0094389

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
============
In BusinessEvents 4.0.1, RequestTimeoutException is thrown when Well Known Addresses(WKAs) are used for starting cluster nodes.

Environment:
==========
TIBCO BusinessEvents


Symptoms:
=========
The following exception is thrown upon starting the engine:

com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster

  MemberSet=ServiceMemberSet(
    OldestMember=n/a
    ActualMemberSet=MemberSet(Size=0, BitSetCount=0
      )
    MemberId/ServiceVersion/ServiceJoined/MemberState
    )
)

    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
    at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
    at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
    at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
    at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
    at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
    at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
    at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:998)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:953)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:892)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:330)
    at com.tibco.cep.runtime.service.om.coherence.cluster.CacheCluster.initCoherence(CacheCluster.java:899)
    at com.tibco.cep.runtime.service.om.coherence.cluster.CacheCluster.initialize(CacheCluster.java:1000)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:871)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:248)
    at com.tibco.cep.container.standalone.BEMain.


Cause:
=====
WKA properties are not specified at cluster level in CDD file.


Resolution:
==========
Specify the WKA properties at the cluster level and also in the CDD file, in addition to the Processing unit level.

Issue/Introduction

In BusinessEvents 4.0.1, RequestTimeoutException is thrown when Well Known Addresses(WKAs) are used for starting cluster nodes.