Getting Started with WebSphere Application Server

More documents

Recommendations

Info

186 Getting Started with WebSphere Application Server Community Edition DefaultThreadPool in the current release. Community Edition might migrate these components to use DefaultThreadPool in the future. 10.3.2 Monitoring thread pools To choose the optimum value for pool sizes, you need to monitor the current utilization of thread pools. You can monitor thread pools using the administrative console: 1. Select the Thread Pools portlet in the console to open the configuration page. A page similar to Figure 10.7 opens. Figure 10.7 - The thread pool configuration page 2. To monitor statistics related to a particular thread pool, click the monitor link corresponding to that pool in the Actions column. A page similar to Figure 10.8 opens. You can monitor the followings statistics: - Pool Max - The maximum number of threads that Community Edition server can create and use in the thread pool. - Lowest Recorded - The lowest number of threads used up to now. - Highest Recorded - The highest number of threads used up to now. - Threads in Use - The number of threads currently in use. Figure 10.8 - Thread pool statistics pane 3. To monitor thread usage of Web connectors, you can still use the monitoring plugin described in section 10.2. Click + besides TomcatAJPConnector, TomcatWebConnector, and TomcatWebSSLConnector to enable monitoring. You can observe the following attributes to monitor the Web container connector’s thread pool as shown in Figure 10.9. - Busy Threads Current - The number of threads currently in use.
Chapter 10 – Tuning a Community Edition server 187 - Busy Threads Max - The highest number of threads used up to now. - Busy Threads Min - The lowest number of threads used up to now. Figure 10.9 - Live statistic information for Web connectors 10.3.3 Configuring the thread pool size Choosing the optimum value for the thread pool size is important to successfully configure the Community Edition server for the best performance. Setting this value too low reduces the throughput because of an increased wait time for a request to be served. Setting it too high reduces the CPU efficiency because of frequent context switching among the threads. You must find the proper balance. You can change thread pool sizes by updating the configuration files. This cannot be done using the administrative console. To apply the required changes: 1. Stop the Community Edition server. 2. Open the /var/config/config.xml with a text editor. 3. To specify the pool size for DefaultThreadPool, insert the following element inside the element. Listing 10.1 provides an example. In the listing, replace xyz with the pool size value you desire. 5000 xyz Listing 10.1 - Specifying a DefaultThreadPool size 4. To specify the pool size for ConnectorThreadPool, insert the following element inside the element. Listing 10.2 provides an example. In the listing, replace xyz with the pool size value you desire.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
5 Chapter 5 - Enterprise Java Beans
Page 91 and 92:
1. Define local and remote interfac
Page 93 and 94:
Chapter 5 - Enterprise Java Beans 9
Page 95 and 96:
Page 97 and 98:
Note: Chapter 5 - Enterprise Java B
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
6 Chapter 6 - Messaging Messaging i
Page 111 and 112:
Chapter 6 - Messaging 111 3. Messag
Page 113 and 114:
Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116:
Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118:
Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120:
Chapter 6 - Messaging 119 For examp
Page 121 and 122:
textMessage.getText()); } catch (JM
Page 123 and 124:
Chapter 6 - Messaging 123 3. Copy t
Page 125:
Chapter 6 - Messaging 125 D. Messag
Page 128 and 129:
128 Getting Started with WebSphere
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137: 136 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182: 10 Chapter 10 - Tuning a Community
Page 183 and 184: Chapter 10 - Tuning a Community Edi
Page 185: Chapter 10 - Tuning a Community Edi
Page 189 and 190: Chapter 10 - Tuning a Community Edi
Page 191 and 192: 10.4.2 Operating system tuning Chap
Page 193: Chapter 10 - Tuning a Community Edi
Page 211 and 212: A Appendix A - Solutions to review
Page 213 and 214: Appendix A - Solutions to review qu
Page 219 and 220: B Appendix B - Up and running with
Page 221 and 222: Appendix B - Up and running with DB
Page 223 and 224: 4. The following is performed by de
Page 235: C Appendix C - Using the sample cod
Page 238 and 239:
Page 240:
show all

Getting Started with WebSphere Application Server

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?