Monitor

Back Next

Sample Dispatch Configurations

This section contains an explanation of some sample dispatch configurations.

Example 1

The following table shows a sample dispatch configuration:

Property	Value
Max Concurrent	15
Max In-Memory	200
Max Queued	1000
Timeout (seconds)	55

The dispatch configuration receives 10,000 requests.

The following table describes the events that occur when each request takes 50 seconds or 60 seconds, and if persistence is enabled or not enabled:

Persistence/Time Taken per request	50	60
Not Enabled	Every 50 seconds, 15 requests move from the Queued column to the Executing Column. The dispatch service processes 200 requests and rejects 9800 requests. Process Server does not execute the rejected messages. All 200 requests are successfully processed because the Timeout value is higher than the time taken to complete a request The value in the consumed column is 200 and the value in the rejected column is 9800. If the Secure Agent restarts before 200 requests are processed, queued requests are lost because they were saved to the in-memory queue and not to the persistent queue.	Every 55 seconds, 15 requests move from the Queued column to the Executing Column. This is because the Timeout value is lower than the time that a request takes to complete. The dispatch service processes 200 requests and rejects 9800 requests. Process Server does not execute the rejected messages. The 200 requests do not complete within the purview of the dispatch service because the Timeout value is lower than the time taken to complete a request. Process Server continues to execute the timed-out messages after the messages leave the dispatch service. The value in the consumed column is 200 and the value in the rejected column is 9800. If the Secure Agent restarts before 200 requests are processed, queued requests are lost.
Enabled	Every 50 seconds, 15 requests move from the Queued column to the Executing Column. The dispatch service processes 1000 requests and rejects 9000 requests. Process Server does not execute the rejected requests. The dispatch service processes 1000 requests successfully because the Timeout value is higher than the time taken to complete a request. The value in the consumed column is 1000 and the value in the rejected column is 9000. If the Secure Agent restarts before 1000 requests are processed, pending requests execute after the restart. This is because requests were saved to the persistent queue.	Every 55 seconds, 15 requests move from the Queued column to the Executing Column. This is because the Timeout value is lower than the time that a request takes to complete. The dispatch service processes 1000 requests and rejects 9000 requests. Process Server does not execute the rejected requests. The 1000 requests do not complete within the purview of the dispatch service because the Timeout value is lower than the time taken to complete a request. Process Server continues to execute the timed-out messages after they leave the dispatch service. The value in the consumed column is 1000 and the value in the rejected column is 9000. The value in the consumed column is 200 and the value in the rejected column is 9800. If the Secure Agent restarts before 1000 requests are processed, pending requests execute after the restart. This is because requests were saved to the persistent queue.

Example 2

The following table shows a sample dispatch configuration:

Property	Value
Max Concurrent	4
Max In-Memory	20
Max Queued	10
Timeout (seconds)	7

The dispatch configuration receives 50 requests.

The following table describes the events that occur when each request takes 50 seconds or 60 seconds, and if persistence is enabled or not enabled:

Persistence/Time Taken per request	5	10
Not Enabled	Every 5 seconds, 4 requests move from the Queued column to the Executing Column. The dispatch service processes 20 requests and rejects 30 requests. Process Server does not execute the rejected requests. The dispatch service successfully processes 20 requests because the Timeout value is higher than the time taken to complete a request The value in the consumed column is 20 and the value in the rejected column is 30. If the Secure Agent restarts before 20 requests are processed, queued requests are lost because they were saved to the in-memory queue and not to the persistent queue.	Every 7 seconds, 4 requests move from the Queued column to the Executing Column. The dispatch service processes 20 requests and rejects 30 requests. Process Server does not execute the rejected requests. The 20 requests do not complete within the purview of the dispatch service because the Timeout value is lower than the time taken to complete a request. Process Server continues to execute the timed-out messages after they leave the dispatch service. The value in the consumed column is 20 and the value in the rejected column is 30. If the Secure Agent restarts before 20 requests are processed, queued requests are lost because they were saved to the in-memory queue and not to the persistent queue.
Enabled	Every 5 seconds, 4 requests move from the Queued column to the Executing Column. The dispatch service processes 20 requests and rejects 30 requests. Process Server does not execute the rejected requests. The dispatch service successfully processes 20 requests because the Timeout value is higher than the time taken to complete a request The value in the consumed column is 20 and the value in the rejected column is 30. If the Secure Agent restarts before 30 requests are processed, pending requests execute after the restart. This is because requests were saved to the persistent queue..	Every 7 seconds, 4 requests move from the Queued column to the Executing Column. The dispatch service processes 20 requests and rejects 30 requests. Process Server does not execute the rejected requests. The 20 requests do not complete within the purview of the dispatch service because the Timeout value is lower than the time taken to complete a request. Process Server continues to execute the timed-out requests after the requests leave the dispatch service. The value in the consumed column is 20 and the value in the rejected column is 30. If the Secure Agent restarts before 30 requests are processed, pending requests execute after the restart. This is because requests were saved to the persistent queue.