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.
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.
- Multithreading and Session in Subscription Service
Configuring multithreading for Subscription Service depends on the session used for this type of service. - Multithreading and Tables for Subscription Service
Multithreading helps improve the performance of Subscription Service, but the improvement is affected by what table structures are selected for the service. You have two table structure options: a single table and a parent-child table.