+

Search Tips   |   Advanced Search

Work manager settings

Use this page to modify work manager settings. Work managers contain a pool of threads that are bound into Java Naming and Directory Interface.

To view this administrative console page, click Resources > Asynchronous beans > Work managers > workmanager_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

Specifies the 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 that we can use to classify or group this work manager.


Work timeout

Number of milliseconds to wait before attempting to release a unit of work. The timeout interval begins when the unit of work starts, rather than when the unit of work is submitted.

Information Value
Default 0
Range 0 to int.maxvalue


Work request queue size

Size of the work request queue.

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.gotcha

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 you submit non-daemon work to the work manager.

If set to FAIL, the 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.

  • Asynchronous beans can inherit J2EE context information by enabling one or more J2EE service contexts on the work manager resource in the WebSphere administrative 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 created using this work manager. Selecting services that are not needed can negatively impact performance.

    Service name Description
    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 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.
    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.


    Thread pool properties

    Priority of the threads available in this work manager.

    Properties Description
    Number of alarm threads Desired maximum number of threads used for alarms.
    Minimum number of threads Minimum number of threads available in this work manager.
    Maximum number of threads Maximum number of threads available in this work manager.
    Thread priority Priority of the threads available in this work manager.
    Growable Whether the number of threads in this work manager can be increased.


    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


    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 concepts

  • Application profiling
  • Internationalization service
  • Java Authentication and Authorization Service


    Related tasks

  • Configure work managers Reference topic