Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Threading Models and Tuning : Event Preprocessor and Rete Worker Thread Options

Event Preprocessor and Rete Worker Thread Options
This aspect of the threading model deals with messages that arrive at destinations. For each destination you choose a threading model type:
The thread used carries execution to the post RTC phase, at which point (except in the case of Caller’s Thread) execution is handed off to one of another set of threads, for writing to cache and backing store, if one is used.
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 FIFO (first in first out).
Additional tuning may be possible at the event level, depending on options available. 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
With this option, all destinations that use the shared queue threading model share the processing unit’s shared queue and threads. (JMS destination is shown as an example). One pool of worker threads picks jobs from the shared queue. Execution continues on a thread through to post-RTC.
This is the default choice. It is the most straightforward option.
In brief the configuration settings are as follows. See Chapter 29, Agent and Processing Unit Configuration inTIBCO BusinessEvents Developer’s Guide for details on these settings
Advantages
Disadvantages
Destination Queue
This option is similar to the Shared Queue option except that each destination has a dedicated thread pool and set of threads to process messages.
Advantages
Disadvantages
Caller’s Thread
The Caller’s Thread option Uses the thread (and queue size) provided by the channel resource client—the Enterprise Message Service client, for example. There is one caller’s thread per destination. The same thread executes the RTC phase.
This option has no tuning controls.
Advantages
Disadvantages

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved