Building Your Event-Driven Architecture : Integration Server Administrator’s Guide : Managing webMethods Messaging Triggers : Managing Document Processing : Increasing or Decreasing Threads for Processing Documents Received by webMethods Messaging Triggers
Increasing or Decreasing Threads for Processing Documents Received by webMethods Messaging Triggers
 
When to Increase or Decrease Threads for Processing Documents
During production and capacity planning, you can increase or decrease the number of threads that can be used to simultaneously process documents received by webMethods messaging triggers. The number of threads available for processing documents helps determine the rate at which Integration Server processes documents. By default, Integration Server can use up to 100% of the server thread pool to process documents (execute triggers). Each time Integration Server processes a document, Integration Server uses a server thread. For example, if the maximum size of the server thread pool is 80 threads, and Integration Server can use 100% of the server thread pool to execute triggers, then up to 80 triggers can execute at the same time. That is, Integration Server can process up to 80 documents simultaneously.
You can control the number of server threads available for document processing (trigger execution) by specifying the maximum percentage of the server thread pool that can be used to process documents. Integration Server uses the percentage to calculate the number of server threads that can be used for trigger execution (document processing). For example, suppose that the maximum size of the server thread pool is 80 threads. If you set 10% as the maximum percentage of document processing threads, then Integration Server can use up to 8 threads simultaneously to execute webMethods messaging triggers.
By reducing the number of server threads used for processing documents, you can make server threads and memory available to perform other tasks, such as executing HTTP requests and retrieving documents. Alternatively, you can increase the number of threads for document processing to allow the server to process more documents simultaneously. This can also allow the server to drain the trigger queues more quickly and request additional documents more frequently.
Document processing for serial and concurrent triggers combined cannot exceed the value determined by the maximum document processing threads percentage. If you reduce the percentage of document processing server threads, and concurrent triggers continue to consume the maximum execution threads possible (according to their configured settings), serial triggers must wait longer for server threads to become available. This is especially likely if Integration Server contains concurrent triggers that execute long-running services.
For more information about setting the number of server threads for document processing, see Limiting Server Threads for webMethods Messaging Triggers.
Tip:  
If you decrease the percentage of threads that can be used for document processing, consider decreasing the Execution Threads Throttle to prevent concurrent triggers from monopolizing available server threads.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback