This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

ThreadPool monitoring

You can use a ThreadPool MXBean for thread pool monitoring in Liberty.

All Web Requests executes in the thread pool, named Default Executor thread pool. You can monitor the usage of Default Executor thread pool using ThreadPoolMXBean.

The ObjectName for identifying MXBean for thread pool is :
WebSphere:type=ThreadPoolStats,name=Default Executor
Key Performance data available for ThreadPool are:
  • Threads in the pool which represents the pool size.
  • Active threads which are serving requests.
Attributes for ThreadPool
  • ActiveThreads
  • PoolSize
  • PoolName (Only supports Default Executor thread pool)
.
Management Interface
The management interface of ThreadPool monitoring is com.ibm.websphere.monitor.jmx.ThreadPoolMXBean. You can use the management interface to obtain a proxy object. See Examples of accessing MBean attributes and operations.
For more information about the management interface, see the Java API document for Liberty. The Java API documentation for each Liberty API is detailed in the Programming Interfaces (APIs) section of the documentation, and is also available as a separate .zip file in one of the javadoc subdirectories of the ${wlp.install.dir}/dev directory.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=rwlp_mon_threadpool
File name: rwlp_mon_threadpool.html