Configuring Multithreading for Subscription Service

To improve the performance in high load scenarios, the adapter uses multiple threads to spread a subscription message load, which prevents blocking the processing on a specific subscription table.

Note: When you configure multithreading in Subscription Service, note the following conditions:
  • TIBCO Hawk statistics display all Subscription Service thread information and operation counts.
  • Debug messages provide Subscription Service thread names to distinguish which message is from which Subscription Service thread.

If a Subscription Service thread encounters fatal errors that the adapter cannot handle, the adapter terminates. Fatal errors include but are not limited to the following ones:

  • Fail to roll back a transaction.
  • Fail to insert received data into the destination table, but the exception table is not configured.
  • Fail to insert error data into the exception table, but the opaque exception table is not configured.
  • Fail to insert error data into the opaque exception table.

The use of multithreading is directly related to the session to be used for Subscription Service. For details, see Multithreading and Session in Subscription Service.

Although multithreading helps improve the performance of Subscription Service, the improvement is affected by what table structures are selected for Subscription Service, a single table or a parent-child table. For details, see Multithreading and Tables for Subscription Service.