WebSphere eXtreme Scale (formerly Data Grid), Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Application thread pools

For applications with computationally expensive operations that process incoming requests from a non-transactional message transport, use a separate worker thread to perform the computation. After receiving the request, create an asynchronous bean work instance and submit the work to a WorkManager to be performed on a separate thread.

When the work completes, continue processing the request. Assume that your application is running on a four-way SMP machine. The WorkManager used for the application should be limited to two threads and should not be expandable, limiting the impact of these long running tasks to two of the four central processing units (CPUs). The remaining two CPUs can be used to schedule the short running tasks.

See the WebSphere Business Integration Sever Foundation documentation for more details, available at http://www.ibm.com/software/integration/wbisf/library/.




Related concepts
General cluster and WPF management considerations
Concept topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 6:09:57 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.dataint.doc/info/WPF51/cwpfasynch_pdf.html