Use this page to modify work manager settings.
A work manager contains a pool of threads bound into JNDI.
To view this administrative console page, click Resources > Work Managers > workmanager_name.
Configuration tab
Default | 0 |
Default | 0 |
If set to FAIL, the work manager API methods creates an exception instead of blocking.
Note: You must set a valid work request queue size in order for the work request queue full action setting to be recognized.
Default | BLOCK |
Range | FAIL |
Asynchronous beans can inherit J2EE context information by enabling one or more J2EE service contexts on the work manager resource in the WebSphere administration console or by setting the serviceNames attribute of the WorkManagerInfo configuration object. When specifying the serviceNames attribute each enabled service should be separated by a semicolon. For example: security;UserWorkArea;com.ibm.ws.i18n. When a J2EE service context is enabled, it propagates the context from the scheduling thread to the target thread. If not enabled, the target thread does not inherit the context of the scheduling thread and a default context is applied. Any related J2EE context that is already present on the thread is suspended before any new J2EE context is applied.
The context information of each selected service is propagated to each work or alarm that is created using this work manager. Selecting services that are not needed can negatively impact performance.
Application profile (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 that are 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. |
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. |
Security | Use the administrative console or the security service name to enable the Java Authentication and Authorization Service (JAAS) subject. When this feature and global 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. |
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. |
Number of alarm threads | Specifies the desired maximum number of threads used for alarms. The default value is 2. |
Minimum number of threads | Specifies the minimum number of threads available in this work manager. |
Maximum number of threads | Specifies the maximum number of threads available in this work manager. |
Thread priority | Specifies the priority of the threads available in this work manager. |
Growable | Specifies whether the number of threads in this work manager can be increased. |