Difference between asserting event and receiving event from channel.
Article ID: KB0090597
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
Difference between asserting event and receiving event from channel.
Environment:
===========
TIBCO BusinessEvents 3.x,4.x
All Operating Systems
Resolution:
========
If an event is asserted during the RTC then it will cause rules to fire because an assertion is a change to the working memory. For example, Event.assertEvent (SimpleEvent event) asserts a SimpleEvent into the working memory. Engine.assertEvent_Async(), asserts a simple event using WorkManager.
However, if an event arrives via a channel to a destination, the destination will start a new RTC and assert the event in the context of that RTC.
Since in-memory OM does not support concurrent WM, it also will wait for the currently running RTC to complete before starting a new RTC.
Description:
===========
Difference between asserting event and receiving event from channel.
Environment:
===========
TIBCO BusinessEvents 3.x,4.x
All Operating Systems
Resolution:
========
If an event is asserted during the RTC then it will cause rules to fire because an assertion is a change to the working memory. For example, Event.assertEvent (SimpleEvent event) asserts a SimpleEvent into the working memory. Engine.assertEvent_Async(), asserts a simple event using WorkManager.
However, if an event arrives via a channel to a destination, the destination will start a new RTC and assert the event in the context of that RTC.
Since in-memory OM does not support concurrent WM, it also will wait for the currently running RTC to complete before starting a new RTC.
Issue/Introduction
Difference between asserting event and receiving event from channel.
Feedback
Yes
No
Powered by
