Description:
Description
=========
In TIBCO BusinessEvents 5.1.1, the Concurrent RTC flag is ignored, if an agent Key is assigned at PU level.

Environment
=========
TIBCO BusinessEvents Version 5.1.1

Symptoms
========
Setting Concurrent RTC flag is ignored, if an agent Key is assigned at PU level.

Without Key, runtime is configured for Concurent RTC and engine runs in that mode as desired.
&ltprocessing-unit id="esePU">
&ltagents>
&ltagent>
&ltref&gteseAgent</ref>
&ltkey/>
&ltpriority/>
</agent>
</agents>

2013 Feb 02 09:14:44:317 GMT +0 ESE1 None [main] - [runtime.session] [eseAgent] Using ObjectManager type :com.tibco.cep.runtime.service.cluster.om.DefaultDistributedCacheBasedStore@2cc0e7ac Concurrent : true
2013 Feb 02 09:14:50:526 GMT +0 ESE1 Info [main] - [runtime.service] --ConcurrentRETE Enabled=true
2013 Feb 02 09:14:52:101 GMT +0 ESE1 Info [main] - [runtime.service] eseAgent: Initializing Rule Session, Working Memory [Concurrent=true]

However, if a Key is defined - then Objectmanager reports the flag as FALSE and runtime does not work in Concurrent mode
&ltprocessing-unit id="esePU">
&ltagents>
&ltagent>
&ltref&gteseAgent</ref>
&ltkey&gtESEPU_ESEAGENT</key>
&ltpriority/>
</agent>
</agents>

2013 Feb 02 09:18:18:334 GMT +0 ESE1 None [main] - [runtime.session] [ESEPU_ESEAGENT] Using ObjectManager type :com.tibco.cep.runtime.service.cluster.om.DefaultDistributedCacheBasedStore@3b4bbe65 Concurrent : false
2013 Feb 02 09:18:24:246 GMT +0 ESE1 Info [main] - [runtime.service] --ConcurrentRETE Enabled=true
2013 Feb 02 09:18:25:822 GMT +0 ESE1 Info [main] - [runtime.service] eseAgent: Initializing Rule Session, Working Memory [Concurrent=true]


Cause
=====
Identified as defect wll be addressed in BE 5.1.1 HF2.

Resolution
========
Defect exists to correct the behavior in a future release.

Workaround
==========

Workaround is to specify the following for each PU:
                &ltproperty name="Agent.&ltagent-key-goes-here>.concurrentwm" value="true"/>

Normally, it is a “checkmark” at Agent definition (which translated to &ltproperty name="Agent.&ltagent-name/id-goes-here>.concurrentwm" value="true"/>)
Symptoms:

Cause:

Concurrent RTC flag is ignored, if an agent Key is assigned at PU level.