Getting Started with WebSphere Application Server

188 Getting Started with WebSphere Application Server Community Edition
5000
xyz
Listing 10.2 - Specifying a DefaultThreadPool size
5. To specify the pool size for connectors of Community Edition Web container,
update the following element inside the
element. Listing 10.3 provides an example. In the listing, replace xyz with the pool
size value you desire. XXX stands for Web, AJP, or WebSSL based on the
different type of Web container connector.
...
PoolSize
...
Listing 10.3 - Specifying a Web connector pool size
6. Save the changes and start the Community Edition server.
7. Verify your changes by:
- Opening the monitoring portlet to monitor the three type thread pool as
described in section 10.2.
- Opening the ConnectorThreadPool page and the DefaultThreadPool
page as described in 10.3.2 Monitoring thread pools
10.4 JVM and operating system tuning
As a Java EE application server, Community Edition runs on a JVM; which runs on the
operating system. In this section, we discuss how to improve Community Edition
performance by tuning JVM and the operating system.
10.4.1 JVM tuning
You may need to customize your Java virtual machine (JVM) to improve the performance
of your server. Below, you will find tips for adjusting the JVM. Keep in mind that the Java
environment may change, making these suggestions obsolete, and that your results can
vary.
10.4.1.1 Monitoring memory usage
It is useful to monitor the current server memory usage before you apply any changes to
the JVM parameters. To analyze the memory, log in to the administrative console and