WebSphere Extended Deployment Compute Grid, Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Managing worker threads

Use this topic to support Object Request Broker (ORB) service advanced settings. The workload profile specifies the server workload profile, which can be ISOLATE, IOBOUND, CPUBOUND, or LONGWAIT.

About this task

Not only does workload management (WLM) dispatch work to servants according to service policy, but it also does so only as long as it has available worker threads. WLM worker threads are regular threads that specifically register with WLM as work receivers. In the WebSphere Application Server for z/OS implementation, this pool of threads is static. The pool in an address space neither grows, nor contracts. The number of worker threads governs the maximum number of concurrent requests that WLM accepts in a servant. However, this applies only to HTTP, IIOP, and Java Message Service (JMS) driven requests. This thread pool does not handle asynchronous beans. The number of threads allocated to this pool is governed by an external object known as the ORB Workload profile.

Procedure

Results

Number of CPUs is the number of CPUs online when the controller starts. You can look at message BBOO0234I in the controller job log to check the number of worker threads.



Related information
ORB services advanced settings on the z/OS platform
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 6:22:31 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.gridmgr.doc/info/scheduler/tzosthreads.html