When to Increase or Decrease Threads for Processing Documents
Your knowledge of your integration solution is the best tool for determining when to adjust thread usage for document processing (trigger execution). For example, suppose that a batch process that occurs at the same time each day results in a spike in document publishing. You might want to increase threads for document processing right before the batch process starts to make server threads available to process documents.
Alternatively, if you observe memory constraints or other resource issues, you can decrease the number of threads for document processing. Document processing consumes memory because Integration Server keeps the document in memory while the server thread evaluates the document and executes the trigger service.
Note:
You can also determine when to modify the number of threads allowed for document processing by monitoring thread usage. You can do this by viewing the thread usage information displayed on the
Server > Statistics page. However, you can also establish a warning threshold that instructs
Integration Server to alert you when the number of available threads drops below a particular level. Specifically,
Integration Server creates a journal log entry stating "
Available Threads Warning Threshold Usage Exceeded." When
Integration Server writes this journal log entry, you might want to decrease threads for document processing to allow more threads to be used for other functions. For more information about setting an available threads warning threshold, see
Managing the Server Thread Pool.
Another way to determine when to alter the number of server threads allotted for processing documents is to monitor the current number of threads that are processing documents for triggers. Integration Server Administrator displays this value in the Current Threads field located under Document Processing on the Messaging > webMethods triggers page.