Techniques For Monitoring Ibm Data Server Driver For Jdbc And Sqlj Connection Concentrator And Workload Balancing - IBM DB2 Manual

|
| |
|
| |
| |
| |
|
|
Techniques for monitoring IBM Data Server Driver for JDBC and SQLJ
connection concentrator and workload balancing
source:
Table 101. Example of data source property settings for IBM Data Server Driver for JDBC
and SQLJ connection concentrator and workload balancing for IBM Informix Dynamic Server
Property
enableSysplexWLB
maxTransportObjects
4. Restart WebSphere Application Server.
To monitor the IBM Data Server Driver for JDBC and SQLJ connection concentrator
and workload balancing, you need to monitor the global transport objects pool.
You can monitor the global transport objects pool in either of the following ways:
v Using traces that you start by setting IBM Data Server Driver for JDBC and
SQLJ configuration properties
v Using an application programming interface
Configuration properties for monitoring the global transport
objects pool
The db2.jcc.dumpPool, db2.jcc.dumpPoolStatisticsOnSchedule, and
db2.jcc.dumpPoolStatisticsOnScheduleFile configuration properties control tracing
of the global transport objects pool.
For example, the following set of configuration property settings cause error
messages and dump pool error messages to be written every 60 seconds to a file
named /home/WAS/logs/srv1/poolstats:
db2.jcc.dumpPool=DUMP_SYSPLEX_MSG|DUMP_POOL_ERROR
db2.jcc.dumpPoolStatisticsOnSchedule=60
db2.jcc.dumpPoolStatisticsOnScheduleFile=/home/WAS/logs/srv1/poolstats
An entry in the pool statistics file looks like this:
time Scheduled PoolStatistics npr:2575 nsr:2575 lwroc:439 hwroc:1764 coc:372
aooc:362 rmoc:362 nbr:2872 tbt:857520 tpo:10
The meanings of the fields are:
npr
The total number of requests that the IBM Data Server Driver for JDBC and
SQLJ has made to the pool since the pool was created.
nsr
The number of successful requests that the IBM Data Server Driver for JDBC
and SQLJ has made to the pool since the pool was created. A successful
request means that the pool returned an object.
lwroc
The number of objects that were reused but were not in the pool. This can
happen if a Connection object releases a transport object at a transaction
boundary. If the Connection object needs a transport object later, and the
original transport object has not been used by any other Connection object, the
Connection object can use that transport object.
Setting
true
100
Chapter 14. JDBC connection concentrator and workload balancing
479