WAS 连接池满的问题跟踪技巧

WAS 连接池满的问题跟踪技巧编制日期：2012-03-10

目录

WAS 连接池满的问题跟踪技巧 (1)

1概述 (3)

2打开连接池跟踪选项 (3)

2.1WAS V5.1 (3)

2.2V7, V6.1 and V6.0 (4)

3分析trace 输出 (5)

1概述

尝试通过如下方法来跟踪jdbc 连接池满的问题：

1、在经常出现问题无法解决的情况下，通过下面描述的方法打开trace选项；

2、出现故障时，将trace文件拷贝到别的机器，避免被冲掉。

3、用下文描述的trace 工具对trace 文件进行分析，看能否找到是什么代码导致连接被长时间调用或者没被释放。

注意事项：

1、根据下文提示，设置足够大的trace文件配额，并保证磁盘空间需要足够。

2、无故障时，应尽量关闭trace，对性能有一定程度的影响。

3、打开trace 开关后，应观察是否确实产生了trace日志。

2打开连接池跟踪选项

2.1 WAS V5.1

In the Application Server Administrative Console, expand Troubleshooting and select Logs and Trace.

a.In the Logging and Tracing page, select your server and then Diagnostic Trace. It is

recommended to set the number of historical trace files to 10 and the size of each historical trace file to

100MB.

b.Ensure that enable trace with the following specification is selected.

c.In the Trace Specification field, enter the following:

▪If connecting to a database in V5.1:

WAS.j2c=all=enabled:

RRA=all=enabled:

WAS.database=all=enabled:

Transaction=all=enabled

▪If connecting to a messaging system in V5.1:

WAS.j2c=all=enabled:

Messaging=all=enabled:

JMSApi=all=enabled:

Transaction=all=enabled

▪If connecting to an enterprise information system in V5.1:

WAS.j2c=all=enabled:

com.ibm.connector2.*=all=enabled:

Transaction=all=enabled

▪

Note: If you are using the V4 data source style, remove the following string in the preceding trace strings:

WAS.j2c=all=enabled:RRA=all=enabled

Then, replace it with the the following trace string:

com.ibm.ejs.cm.*=all=enabled

d.Under Trace Output, select File, and accept the defaults.

e.Click OK and save your configuration.

f.Restart the Application Server.

g.Reproduce the problem.

h.Send the resulting trace output file.

2.2 V7, V6.1 and V6.0

For releases of V7, V6.1 and V6.0:

a.In the Application Server Administrative Console, expand Troubleshooting and select Logs

and Trace.

b.In the Logging and Tracing page, select your server and then Diagnostic Trace.

c.Ensure that Enable Log is selecte

d.

d.Under Trace Output, select File, and accept the defaults. It is recommended to set the number

of historical trace files to 10 and the size of each historical trace file to 100MB.

e.Click OK and save your configuration.

f.Again, expand Troubleshooting and select Logs and Trace.