Resolution:
Description:
===========
Exception “JMS TopicConnectionFactory is null while Topic destination is configured”  thrown when starting the be-engine.

Environment:
===========
TIBCO BusinessEvents 5.x
All Operating Systems


Symptoms:
=========
2013 Oct 20 14:36:34:350 GMT +5 LocalMachine Info [main] - [driver.jms] Connecting JMS Channel [/Channels/FulfillmentServiceJMSChannel] Properties [JNDI=tibjmsnaming://local-t420:7222 QCF=XL_SOAR_JMS_SERVICE_QUEUE_01 TCF=XL_SOAR_JMS_SERVICE_TOPIC_01 user=admin clientID=BE-EBMEngine_XL-Localmachine-/Channels/FulfillmentServiceJMSChannel] [Thread: main] [State: Initialized]

2013 Oct 20 14:36:34:409 GMT +5 LocalMachine Fatal [main] - [container.standalone] JMS TopicConnectionFactory is null while Topic destination is configured.

javax.jms.JMSException: JMS TopicConnectionFactory is null while Topic destination is configured.

    at com.tibco.cep.driver.jms.JMSChannel.createConnectionFactories(SourceFile:151)

    at com.tibco.cep.driver.jms.BaseJMSChannel.connect(SourceFile:236)

    at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.connectChannels(ChannelManagerImpl.java:246)

    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:699)

    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:271)

    at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:149)

    at com.tibco.cep.container.standalone.BEMain.main(SourceFile:69)

System exit requested by thread [main] with status: -1

System.exit(..) will be invoked now with status: -1

Cause:
======
Wrong configuration.

Resolution:
===========

This exception will happen when you configure a TopicConnectionFactory with a QueueConnectionFactory. Check all JMS Connection Factories for correct values.