Task Admin Page

You can view Service invocation status data on the Task Admin page, which can be helpful when troubleshooting Service execution. Normally, Service invocation data is purged after a Service has completed. This can be changed by setting the PURGE_INVOCATION_DATA Service option. This data is stored in memory on the Broker, so this setting might need to be modified depending on how the Service is used. The following options are available:

•

INVOCATION_COMPLETED — data for each request is purged as soon as the request has completed. In this case, the data is only available when the request is queued or being processed. This must be used when the Service might be a long-running open Service, as each entry requires memory.

•

INVOCATION_COMPLETED_SUCCESSFULLY — data for each request is purged as soon as it has completed, but only if the request was successfully completed. This is useful when diagnosing failure of long-running Services.

•

SERVICE_COMPLETED — data is purged when the Service instance has completed. As long as the instance is running, the data is available. This is the default.

•

SERVICE_REMOVED — data is removed when the completed Service instance is removed from the Admin interface. This enables you to view data after an instance completes, at the cost of memory overhead on the Broker. The instance is removed either automatically according to the Service Cleanup settings on the Broker, or when it is manually removed.