Resolution:
Error stack trace when starting the BusinessEvents Engine.

2008 May 27 14:10:41:487 GMT -5 TEPA-2-P Error
[FTAsyncQueueManager:TEPA-2-P] - Failed to initialize RuleSessions
com.tibco.cep.runtime.service.om.OMException:
java.lang.IllegalStateException: Service "DistributedCache" has been
started by the factory with a different configuration descriptor
        at
com.tibco.cep.runtime.service.om.coherence.CoherenceStore.startAllCaches
(CoherenceStore.java:1061)
        at
com.tibco.cep.runtime.service.om.coherence.CoherenceStore.recover(Cohere
nceStore.java:1244)

Resolution

======= 

This issue happens if using an older coherence-cache-config.xml (older than the one in BE 2.2) in your project and if you are using Coherence and FaultTolerence together in your setup. In BE 2.2, the following Cache Scheme has been added in the coherence-cache-config.xml which is used for FT cache.

<cache-mapping>
      <cache-name>$FT*</cache-name>
      <scheme-name>ft-replicated</scheme-name>
</cache-mapping>

BE 2.1.x coherence-cache-config.xml does not have the above caching scheme. If you use the BE 2.1.1 coherence-cache-config.xml in BE 2.2, the BE engine will not find the required FT caching scheme and will use the default distributed cache. This will cause a clash since both the OM Cache and FT Cache will use the same service name "DistributedCache". To avoid this issue you should use the correct coherence-cache-config.xml shipped with BE 2.2. Also, to address this issue, the following engine property was introduced in BE 2.2 HF1, which enables you to specify the fully qualified path to the customized cache configuration file:

java.property.tangosol.coherence.cacheconfig

When using the property tangosol.coherence.cacheconfig, any cache configuration specified in BusinessEvents Archive OM configuration, i.e. Shared Resource or File URI, is overridden.

java.lang.IllegalStateException when starting the TIBCO BusinessEvents Engine.