Getting Started with WebSphere Application Server

Chapter 10 – Tuning a Community Edition server 185
Figure 10.6 - Live statistics
Similarly, you can easily monitor TransactionManager, Tomcat connector, and Web apps in
Community Edition.
This section provided a quick introduction to monitoring a Community Edition server with
the monitoring plug-in. The monitoring plug-in has other powerful functions such as
visualization of the history data of server statistics. For a complete reference about the
monitoring plug-in, visit
http://publib.boulder.ibm.com/wasce/V2.1.1/en/monitoring-the-health-of-a-server.html
10.3 Community Edition Server tuning
In this section we describe parameters of a Community Edition server that you can monitor
and modify to improve the performance.
10.3.1 Thread pool size
The thread pool size determines the processing capacity of a Community Edition server.
Tuning this parameter is important to achieve the best performance. The Community
Edition server allows the customization of three types of thread pools:
• DefaultThreadPool is the major thread pool in Community Edition; it specifies the
maximum number of threads possible in the server. Its default size is 500.
• ConnectorThreadPool is used by the connector including JMS, Data source, and
other JCA connectors in the server. Its default size is 30.
• Web container connector thread pool. Each connector of Web container has its
own thread pool. Its default value varies for different Web connector types.
Note:
DefaultThreadPool is the major thread pool in Community Edition; however, some
components including the Community Edition Web container are not using