Event Preprocessor and Rete Worker Thread Options
Event Preprocessor and Rete Worker Thread Options deal with messages that arrive at destinations.
For each destination you need to choose on of the threading model types:
A thread carries execution to the post RTC phase, at which point execution for the Shared and Destination Queue thread is handed off to another set of threads for writing to cache and backing store. In all threading models, event preprocessing is multi-threaded for high performance.
Diagrams in this section use as an example EMS messages, arriving at JMS destinations.
Each JMS destination creates a separate JMS Session internally, and creates a JMS thread for itself. All queues in all options are blocking, and follow FIFO (first in first out).
Additional tuning may be possible at the event level. For example, the Enterprise Message Service server queue can be sized appropriately. This topic is outside the scope of TIBCO BusinessEvents documentation.
Note that for events sent out in the event preprocessor phase messages are sent immediately, and for events sent out during the RTC messages are sent in the post RTC phase.
- Shared Queue
All destinations that use the shared queue threading model share the processing unit’s shared queue and threads. - Destination Queue
The Destination Queue option is similar to the Shared Queue option except that each destination has a dedicated thread pool and set of threads to process messages. - Caller’s Thread
The Caller’s Thread option uses the thread (and queue size) provided by the channel resource client, such as the Enterprise Message Service client.