Used in: caching-schemes.
Defines an Invocation Service. The invocation service may be used to perform custom operations in parallel on any number of cluster nodes. See the com.tangosol.net.InvocationService API for additional details.
The following table describes the elements you can define within the invocation-scheme element.
| Element | Required/Optional | Description |
|---|---|---|
| <scheme-name> | Optional | Specifies the scheme's name. The name must be unique within a configuration file. |
| <scheme-ref> | Optional | Specifies the name of another scheme to inherit from. |
| <service-name> | Optional | Specifies the name of the service which will manage invocations from this scheme.
services are configured from within the operational descriptor. |
| <thread-count> | Optional | Specifies the number of daemon threads used by the invocation service.
If zero, all relevant tasks are performed on the service thread. Legal values are positive integers or zero. Default value is the value specified in the tangosol-coherence.xml descriptor. |
| <autostart> | Optional | The autostart element is intended to be used by cache servers (i.e. com.tangosol.net.DefaultCacheServer). It specifies whether or not this service should be automatically started at a cluster node.
Legal values are true or false. Default value is false. |
| <task-hung-threshold> | Optional | Specifies the amount of time in milliseconds that a task can execute before it is considered "hung". Note: a posted task that has not yet started is never considered as hung. This attribute is applied only if the Thread pool is used (the "thread-count" value is positive).
Legal values are positive integers or zero (indicating no default timeout). Default value is the value specified in the tangosol-coherence.xml descriptor. |
| <task-timeout> | Optional | Specifies the default timeout value in milliseconds for tasks that can be timed-out (e.g. implement the com.tangosol.net.PriorityTask interface), but don't explicitly specify the task execution timeout value. The task execution time is measured on the server side and does not include the time spent waiting in a service backlog queue before being started. This attribute is applied only if the thread pool is used (the "thread-count" value is positive).
Legal values are positive integers or zero (indicating no default timeout). Default value is the value specified in the tangosol-coherence.xml descriptor. |
| <request-timeout> | Optional | Specifies the default timeout value in milliseconds for requests that can time-out (e.g. implement the com.tangosol.net.PriorityTask interface), but don't explicitly specify the request timeout value. The request time is measured on the client side as the time elapsed from the moment a request is sent for execution to the corresponding server node(s) and includes the following:
(1) the time it takes to deliver the request to an executing node (server); Legal values are positive integers or zero (indicating no default timeout).
|