Work manager settings
Modify work manager settings. Work managers contain a pool of threads that are bound into Java Naming and Directory Interface.
From the admin console, click...
Resources > Concurrency > Work managers > work_manager_name.
Scope
Scope of the configured resource. This value indicates the location for the configuration file.
Name
Unique name by which the work manager is known for administrative purposes.
Work manager processing requires that the work manager have a unique name.
JNDI name
JNDI name used to look up the work manager in the namespace.
Description
Description of this work manager for administrative purposes.
Category
Specifies a string we can use to classify or group this work manager.
Work timeout
Number of milliseconds to wait before attempting to cancel or release a unit of work. The timeout interval begins when the unit of work starts, rather than when the unit of work is submitted. Work timeout applies to Asynchronous Beans work, CommonJ work, and managed executor tasks submitted via execute/submit, but not via invokeAll/invokeAny, which have their own mechanism for specifying a timeout.
| Information | Value |
|---|---|
| Default | 0 |
| Range | 0 to int.maxvalue |
Work request queue size
Size of the work request queue.
Avoid trouble: The work request queue is a buffer that holds scheduled work objects and can be a value of 1 or greater. The thread pool pulls work from this queue. If we do not specify a value or the value is 0, the queue size is managed automatically. When the queue size is managed
automatically, it is computed as the larger of (maximum_number_of_threads) or 20.
Large values can consume significant system resources.
| Information | Value |
|---|---|
| Default | 0 |
Work request queue full action
Action taken when the thread pool is exhausted, and the work request queue is full. This action starts when we submit non-daemon work to the work manager.
If set to FAIL, the executor or work manager API methods creates an exception instead of blocking.
| Information | Value |
|---|---|
| Default | BLOCK |
| Range | FAIL |
Service names
List of services to make available to this work manager.
Tasks submitted by a work manager can inherit thread context information by enabling one or more service contexts on the work manager resource in the administrative console or by setting the serviceNames attribute of the WorkManagerInfo configuration object. When specifying the serviceNames attribute, separate each enabled service by a semicolon; for example: security;UserWorkArea;com.ibm.ws.i18n. Thread context information is inherited from the submitting thread or from the thread that looked up or injected a managed thread factory.
When a service context is enabled, it propagates the context to the target thread from the scheduling thread or from the thread that looked up or injected the managed thread factory. If not enabled, the target thread does not inherit the context of the scheduling thread and a default context is applied. Any related context already present on the thread is suspended before any new context is applied.
The context information of each selected service is propagated to each callable, runnable, managed thread, contextual proxy, work or alarm created using this work manager. Selecting services that are not needed can negatively impact performance.
| Service name | Description |
|---|---|
| Internationalization | Use the administrative console or the com.ibm.ws.i18n service name to enable the internationalization context information. When the internationalization context and the Internationalization service is enabled, the internationalization context that exists on the scheduling thread is available on the target thread. This feature is optional. |
| Security | Use the administrative console or the security service name to enable the JAAS subject. When this feature and administrative security are enabled, the JAAS subject that is present on the scheduling thread is applied to the target thread. If not enabled, the target thread is run anonymously without a JAAS subject on the thread. This feature is optional. |
| Work area | Use the administrative console or the UserWorkArea service name to enable work area
partitions. When enabled, the work area context for every work area partition that exists on the scheduling thread is available on the target thread. This feature is optional. |
| Application profiling service (deprecated) | Use the administrative console or the AppProfileService service name to enable the application profile tasks. Application profile context is not supported and not available for J2EE 1.4 applications. For J2EE 1.3 applications, the application profile context is deprecated and is only available when Application Profile Service 5.x Compatibility Mode is enabled and both the scheduling thread and target thread are J2EE 1.3 applications. When enabled, all application profile tasks available on the scheduling thread are available on the target thread. The scheduled work that runs in a J2EE 1.4 application does not get the application profiling task of the scheduling thread. This feature is optional. |
Thread pool properties
Specifies properties to control thread pool behavior.
| Properties | Description |
|---|---|
| Number of alarm threads | Desired maximum number of threads for a separate thread pool for tasks and alarms that are scheduled to run at a specific point in time. |
| Minimum number of threads | work manager for submitted tasks that are to run immediately. This property does not apply to tasks scheduled to run at a specific point in time. |
| Maximum number of threads | Maximum number of threads available in this work manager for submitted tasks that are to run immediately. This property does not apply to tasks scheduled to run at a specific point in time. |
| Thread priority | Priority of the threads available in this work manager. This property includes both pooled threads and threads created by a managed thread factory. |
| Growable | Specifies whether the number of threads in this work manager can be increased. |
(ZOS)
Default transaction class
Transaction class name used to classify work run by this work manager instance when the z/OS Work Load Manager Service class information is not contained in the work context information.
| Information | Value |
|---|---|
| Data type | String |
| Range | 0-8 characters |
(ZOS)
Daemon transaction class
Transaction class used for the Work Load Manager Service workload classification of daemon work.
| Information | Value |
|---|---|
| Data type | String |
| Range | 0-8 characters |
Related: