Resolution:
Description:
============
In TIBCO BusinessEvents (BE) , starting Cache agent fails with the CDD exception.

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

Symptoms:
========
Using property file: C:\tibco_be\be\4.0\bin\be-engine.tra
java.lang.RuntimeException: Cannot read CDD: Deployments\Archive\PCM_CDD.cdd
        at com.tibco.cep.runtime.session.RuleServiceProviderManager.createBEProperties(RuleServiceProviderManager.java:80)
        at com.tibco.cep.runtime.session.RuleServiceProviderManager.newProvider(RuleServiceProviderManager.java:381)
        at com.tibco.cep.container.standalone.BEMain.jumpStart(BEMain.java:104)
        at com.tibco.cep.container.standalone.BEMain.main(BEMain.java:52)
Caused by: com.tibco.xml.validation.exception.UnexpectedEndException: unexpected end of content; expected {http://tibco.com/businessevents/configurati
on/4.0.0/2009/11/25}alert-config
        at com.tibco.xml.channel.remark.helpers.XmlRemarkToError.error(XmlRemarkToError.java:148)
        at com.tibco.xml.validation.state.driver.ValidationJazz.a(ValidationJazz.java:472)
        at com.tibco.xml.validation.state.driver.ValidationJazz.endElement(ValidationJazz.java:512)
        at com.tibco.xml.validation.state.glue.SaxValidationDriver.endElement(SaxValidationDriver.java:95)
        at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
        at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at com.tibco.xml.datamodel.parse.DefaultXiParser.a(DefaultXiParser.java:209)
        at com.tibco.xml.datamodel.parse.DefaultXiParser.parse(DefaultXiParser.java:222)
        at com.tibco.xml.datamodel.parse.DefaultXiParser.parse(DefaultXiParser.java:176)
        at com.tibco.be.util.config.factories.ClusterConfigFactory.newConfig(ClusterConfigFactory.java:69)
        at com.tibco.be.util.config.factories.ClusterConfigFactory.newConfig(ClusterConfigFactory.java:59)
        at com.tibco.cep.runtime.session.RuleServiceProviderManager.readCdd(RuleServiceProviderManager.java:249)
        at com.tibco.cep.runtime.session.RuleServiceProviderManager.createBEProperties(RuleServiceProviderManager.java:77)
        ... 3 more
Caused by: com.tibco.xml.validation.exception.UnexpectedEndException: unexpected end of content; expected {http://tibco.com/businessevents/configurati
on/4.0.0/2009/11/25}alert-config
        at com.tibco.xml.validation.state.a.b.a(CMElementValidationState.java:474)
        at com.tibco.xml.validation.state.a.b.a(CMElementValidationState.java:270)
        at com.tibco.xml.validation.state.driver.ValidationJazz.endElement(ValidationJazz.java:495)
        ... 21 more


Cause:
=====
The exception can be due to a few reasons.

1).The engine is not able to read the cdd file.

2). Cache PU name change is different from the name that is given to start the engine. For example, If the cache PU name in the cdd file is Cache-test and the engine is started using

be-engine.exe -c C:\401testing\401hHF1\FraudDetectionCache\fdcache.cdd -u cache c:\temp\fdcache.ear.


Resolution:
==========
1).Give the correct and complete path of  the cdd file.

2).Giving the same name in the command line for the processing unit as given in the  cdd file for cache PU.