The following exception is thrown while starting up the Cache Engine. "java.lang.RuntimeException: Entity DAO does not exists for class:be.gen.Events.STTTimeoutEvent".
Article ID: KB0093245
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
During Cache Engine startup, the following exception is thrown. "java.lang.RuntimeException: Entity DAO does not exists for class:be.gen.Events.STTTimeoutEvent" .
com.tibco.cep.common.exception.LifecycleException: com.tibco.cep.common.exception.LifecycleException: java.lang.RuntimeException: Entity DAO doesnot exists for class:be.gen.Events.STTTimeoutEvent
at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.startCluster(RuleServiceProviderImpl.java:794)
...
Caused by: com.tibco.cep.common.exception.LifecycleException: java.lang.RuntimeException: Entity DAO doesnot exists for class:be.gen.Events.STTTimeoutEvent
at com.tibco.cep.runtime.service.cluster.MultiAgentCluster.start(MultiAgentCluster.java:257)
...
Caused by: java.lang.RuntimeException: Entity DAO doesnot exists for class:be.gen.Events.STTTimeoutEvent
at com.tibco.cep.runtime.service.cluster.system.MetadataCache.getEntityDao(MetadataCache.java:672)
+++++
Symptoms:
During Cache Engine startup, the following exception is thrown. "java.lang.RuntimeException: Entity DAO doesnot exists for class:be.gen.Events.STTTimeoutEvent".
Cause:
The discover/listening URLs were colliding with other environments. Because of this, the current environment cluster was trying to join other environments resulting in the exception.
Resolution
Specify unique discover/listen URLs.
Issue/Introduction
The following exception is thrown while starting up the Cache Engine. "java.lang.RuntimeException: Entity DAO does not exists for class:be.gen.Events.STTTimeoutEvent".
Additional Information
More detailed information related to be.engine.cluster.as.discover.url settings can be found in the manual (TIBCO BusinessEvents Developers Guide, Chapter "Configuring Cluster Discovery and Internal Communication").
Feedback
Yes
No
Powered by
