Resolution:
Description:
=========
Using TOPIC as BusinessEvents(BE) destination. When attempting to test the BE inference engine in Debugger, the following exception was seen and the Engine did not start properly.

Exception from console:
>>>>>>>>>>>>>>>>>>
2010 Sep 06 11:52:00:547 GMT +8 apandian-nb.apac.tibco.com Debug [main] - [kernel.core] [OrderTxnAgent] Rule loaded: /Rules/TestRule
2010 Sep 06 11:52:00:563 GMT +8 apandian-nb.apac.tibco.com Info [main] - [kernel.core] [OrderTxnAgent] Rule deployed: /Rules/TestRule
2010 Sep 06 11:52:00:578 GMT +8 apandian-nb.apac.tibco.com Debug [main] - [modules.db] DB Concepts disabled, connection pool not started.
2010 Sep 06 11:52:00:672 GMT +8 apandian-nb.apac.tibco.com Info [main] - [driver.jms] Connecting JMS Channel [/Channels/JMSChannel] Properties [serverURL=tcp://localhost:7222 user=admin clientID=] [Thread: main] [State: Initialized]
2010 Sep 06 11:52:00:860 GMT +8 apandian-nb.apac.tibco.com Debug [main] - [runtime.session] OrderTxnAgent binding input channel /Channels/JMSChannel/AllOrderTxnMsgs to destination /Channels/JMSChannel
2010 Sep 06 11:52:00:875 GMT +8 apandian-nb.apac.tibco.com Info [main] - [driver.jms] Destination [/Channels/JMSChannel/AllOrderTxnMsgs] Properties [Name=ORDER02.* Selector= Priority=4 Queue=false TTL=0 DeliveryMode=1 AckMode=1 Serializer=com.tibco.cep.driver.jms.serializer.TextMessageSerializer]
2010 Sep 06 11:52:00:875 GMT +8 apandian-nb.apac.tibco.com Info [main] - [driver.jms] Destination [/Channels/JMSChannel/AllOrderTxnMsgs] Listener started for RuleSession [OrderTxnAgent]
2010 Sep 06 11:52:00:875 GMT +8 apandian-nb.apac.tibco.com Info [main] - [driver.jms] Started Channel [/Channels/JMSChannel]
2010 Sep 06 11:52:00:922 GMT +8 apandian-nb.apac.tibco.com Debug [main] - [kernel.core] [OrderTxnAgent] RTC Operations: [Object=AdvisoryEvent@id=2, RtcOps=101]
2010 Sep 06 11:52:01:016 GMT +8 apandian-nb.apac.tibco.com Warning [main] - [driver.jms] Exception while creating consumer, it could be configuration issue or JMS Server connection severed on the primary, retrying: 1
2010 Sep 06 11:52:02:016 GMT +8 apandian-nb.apac.tibco.com Warning [main] - [driver.jms] Exception while creating consumer, it could be configuration issue or JMS Server connection severed on the primary, retrying: 2
<<<<<<<<<<<<

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

Cause:
======
This error might happen when trying to start different subscribers with the same subscriber name.
  
Resolution:
=========  
Check on your side:
  - if there are multiple be-engine started with the same ear file.
  - if the second engine is started with the same subscriber name.
  
If multiple be-engines need to be started with the same ear file, you can set a different name for each engine (do so by starting be-engine from command line with -n differntEngineName for each engine).

BusinessEvents(BE) Infrence Engine had problem in connecting with EMS Channel: Warning [main] - [driver.jms] Exception while creating consumer, it could be configuration issue or JMS Server connection severed on the primary.