Search

Monitor

Monitor

Back Next

Monitoring a Dispatch Configuration

Monitoring a Dispatch Configuration

Use the

Dispatch Queue

page to monitor dispatch configurations

The following table describes the columns that on the

Dispatch Queue

page:

Column	Description
Name	The dispatch configuration name.
Executing	The number of requests running under the dispatch configuration.
Queued	The number of requests queued by the dispatch configuration. Requests move from Queued to Executing when any of the following events occur: A request completes. A request times out. A request moves out of the queue because you purged queued requests.
Average Time (ms)	The average time, in milliseconds, for which a listener in the concurrent pool works on a request.
Consumed	The number of requests that have passed through the dispatch configuration. This number does not include rejected messages.
Rejected	The number of requests that were rejected by the dispatch configuration. This number does not include timed out requests. For details, see Timeout (Seconds).
Status	The status of the dispatch configuration. A dispatch configuration can be in the following states: Active: The dispatch configuration is running and can send queued requests to Process Server. Suspended: The dispatch configuration is paused. Pending queued requests remain in the queue until dispatch configuration is resumed. Pending Delete: There are queued requests that need to be consumed. If you see this status, delete the dispatch configuration and refresh the browser.

The following table describes the actions that you can take on one a dispatch configuration:

Action	Description
Reset Statistics	Sets the Executing and Average Time (ms) values to zero.
Suspend Execution	Stops sending requests to Process Server. Requests remain in a queue until you resume the dispatch configuration.
Resume Execution	Resumes dispatching new requests to the engine.
Purge Queued Requests	Deletes all pending requests from the in-memory queue and the persistent queue. Process Server does not execute these requests. Use this action in unusual circumstances that require clearing the queue.
Delete Configuration	Removes the dispatch configuration. The status will be Pending Delete until you refresh the browser. Requests do not go to Process Server after you select Delete Configuration . If there are queued requests, the configuration is removed after all requests are consumed.

Dispatch Service

Watch

Comments

Cloud Application Integration Homepage

0 COMMENTS

We’d like to hear from you! Log in to comment.