Replication Server runs multiple threads concurrently. The total number of threads depends on the number of databases that a Replication Server manages and the number of Replication Servers to which it has direct routes. Each thread performs a specific function such as managing a user session, receiving messages from a RepAgent, receiving messages from another Replication Server, or applying transactions to databases.
Some threads call specific portions (or “modules”) of Replication Server to determine the destination of messages and transactions, and to determine what operations to replicate and how to replicate them.
Daemon threads, which run in the background and perform specified operations at predefined times or in response to certain events, run during such Replication Server activities as subscription materialization.
For details on Replication Server threads, modules, and daemons involved in processes specific to the primary Replication Server, see “Processing in the primary Replication Server”.
When you troubleshoot the replication system, verify the status of Replication Server threads, modules, and daemons. See Chapter 1, “Verifying and Monitoring Replication Server” for details.
