方式一:
在Spring的"applicationContext.xml"中的dataSource bean定义——
class ="org.logicalcobwebs.proxool.ProxoolDataSource" >
< property name ="driver" >
< value >com.mysql.jdbc.Driver </ value >
</ property >
< property name ="driverUrl" >
< value >jdbc:mysql://localhost:3306/dbname?user=yourname &password=yourpass </ value >
</ property >
< property name ="user" value ="yourname" />
< property name ="password" value ="yourpass" />
< property name ="alias" value ="Pool_dbname" />
< property name ="houseKeepingSleepTime" value ="90000" />
< property name ="prototypeCount" value ="0" />
< property name ="maximumConnectionCount" value ="50" />
< property name ="minimumConnectionCount" value ="2" />
< property name ="simultaneousBuildThrottle" value ="50" />
< property name ="maximumConnectionLifetime" value ="14400000" />
< property name ="houseKeepingTestSql" value ="select CURRENT_DATE" />
</ bean >
第一种方式需要把用户名和密码写在连接串里面,
ProxoolDataSource类提供的user,password属性似乎没有什么用。
无论提供什么,它都会以空用户名、密码去连接数据库。
这可能是Proxool RC0.93的一个bug,实在让人恼火,但是最新的0.9.1已经没有这个bug。
不过配置中的user,password两个属性还必须设置,否则hibernate会报空指针错误。
在新的Proxool 0.9.1中houseKeepingSleepTime和 maximumConnectionLifetime 属性设置的值出错需要自己修改修改方法如下:
public class ProxoolDataSources extends ProxoolDataSource {
private long maximumConnectionLifetime;
private long houseKeepingSleepTime;
public long getMaximumConnectionLifetime() {
return maximumConnectionLifetime;
}
public void setMaximumConnectionLifetime(long maximumConnectionLifetime) {
this.maximumConnectionLifetime = maximumConnectionLifetime;
}
public long getHouseKeepingSleepTime() {
return houseKeepingSleepTime;
}
public void setHouseKeepingSleepTime(long houseKeepingSleepTime) {
this.houseKeepingSleepTime = houseKeepingSleepTime;
}
方式二:
在Spring的"applicationContext.xml"中的dataSource bean定义——
class ="org.springframework.jdbc.datasource.DriverManagerDataSource" >
< property name ="driverClassName" >
< value >org.logicalcobwebs.proxool.ProxoolDriver </ value >
</ property >
< property name ="url" >
< value >proxool.Pool_dbname </ value >
</ property >
</ bean >
第二种方式需要预先在"web.xml"先配置好Proxool连接池,配置如下:
< servlet-name >proxoolServletConfigurator </ servlet-name >
< servlet-class >
org.logicalcobwebs.proxool.configuration.ServletConfigurator
</ servlet-class >
< init-param >
< param-name >xmlFile </ param-name >
< param-value >WEB-INF/proxool.xml </ param-value >
</ init-param >
< load-on-startup >1 </ load-on-startup >
</ servlet >
< servlet >
< servlet-name >context </ servlet-name >
< servlet-class >
org.springframework.web.context.ContextLoaderServlet
</ servlet-class >
< load-on-startup >2 </ load-on-startup >
</ servlet >
注意,第二种方式下Spring的上下文加载如果想使用listener方式(Struts2要求),
则与连接池有关的Bean全得延迟初始化。因为listener比servlet优先初始化,
如果相关Bean不是lazy-init的话,则启动服务器时会出现Bean找不到连接定义的异常。
<listener>
<listener-class>
org.springframework.web.context.ContextLoaderListener
</listener-class>
</listener>
其中proxool的配置文件可以采用xmlFile"proxool.xml"或者propertyFile"proxool.properties"
"proxool.xml"格式如下:
< proxool-config >
< proxool >
< alias >Pool_dbname </ alias >
< driver-url >jdbc:mysql://localhost:3306/dbname </ driver-url >
< driver-properties >
< property name ="user" value ="yourname" />
< property name ="password" value ="yourpass" />
</ driver-properties >
< house-keeping-sleep-time >60000 </ house-keeping-sleep-time >
< maximum-connection-count >20 </ maximum-connection-count >
< minimum-connection-count >2 </ minimum-connection-count >
< prototype-count >0 </ prototype-count >
< simultaneous-build-throttle >20 </ simultaneous-build-throttle >
< house-keeping-test-sql >select CURRENT_DATE </ house-keeping-test-sql >
< statistics >15s,10m,1d </ statistics >
< statistics-log-level >INFO </ statistics-log-level >
</ proxool >
< proxool >
<!-- 可以配置多个库 -->
</ proxool >
</ proxool-config >
"proxool.properties"格式如下:
jdbc-0.proxool.driver-url=jdbc:mysql://localhost:3306/dbname
jdbc-0.proxool.driver-class=com.mysql.jdbc.Driver
jdbc-0.user=yourname
jdbc-0.password=yourpass
jdbc-0.proxool.house-keeping-sleep-time=60000
jdbc-0.proxool.house-keeping-test-sql=select CURRENT_DATE
jdbc-0.proxool.maximum-connection-count=10
jdbc-0.proxool.minimum-connection-count=3
jdbc-0.proxool.maximum-connection-lifetime=18000000
jdbc-0.proxool.prototype-count=3
jdbc-0.proxool.simultaneous-build-throttle=10
jdbc-0.proxool.recently-started-threshold=60000
jdbc-0.proxool.overload-without-refusal-lifetime=50000
jdbc-0.proxool.maximum-active-time=60000
jdbc-0.proxool.verbose=true
jdbc-0.proxool.trace=true
jdbc-0.proxool.fatal-sql-exception=Fatal error
jdbc-2.proxool.alias=Pool_dbname2
……
<!--可以配置多个库-->
三、更详细的proxool.xml的配置属性说明:
- <?xml version="1.0" encoding="ISO-8859-1"?><!--
- Properties for Proxool Configurator testing. Defines the same parameters as
- TestHelper.buildCompleteAlternativeProperties()
- -->
- <something-else-entirely xmlns="http://sumthin.else.entirely" xmlns:proxool="The latest version is available at http://proxool.sourceforge.net/xml-namespace">
- <proxool:proxool>
- <proxool:alias>xml-test-ns</proxool:alias>
- <proxool:driver-url>jdbc:hsqldb:db/test</proxool:driver-url>
- <proxool:driver-class>org.hsqldb.jdbcDriver</proxool:driver-class>
- <proxool:driver-properties>
- <proxool:property name="user" value="sa"/>
- <proxool:property name="password" value=""/>
- </proxool:driver-properties>
- <proxool:house-keeping-sleep-time>40000</proxool:house-keeping-sleep-time>
- <proxool:house-keeping-test-sql>select CURRENT_DATE</proxool:house-keeping-test-sql>
- <proxool:maximum-connection-count>10</proxool:maximum-connection-count>
- <proxool:minimum-connection-count>3</proxool:minimum-connection-count>
- <proxool:maximum-connection-lifetime>18000000</proxool:maximum-connection-lifetime> <!-- 5 hours -->
- <proxool:simultaneous-build-throttle>5</proxool:simultaneous-build-throttle>
- <proxool:recently-started-threshold>40000</proxool:recently-started-threshold>
- <proxool:overload-without-refusal-lifetime>50000</proxool:overload-without-refusal-lifetime>
- <proxool:maximum-active-time>60000</proxool:maximum-active-time>
- <proxool:verbose>true</proxool:verbose>
- <proxool:trace>true</proxool:trace>
- <proxool:fatal-sql-exception>Fatal error</proxool:fatal-sql-exception>
- <proxool:prototype-count>2</proxool:prototype-count>
- </proxool:proxool>
- <nothing-to-do-with-proxool>
- <proxool:proxool>
- <proxool:alias>xml-test-ns-2</proxool:alias>
- <proxool:driver-url>jdbc:hsqldb:db/test</proxool:driver-url>
- <proxool:driver-class>org.hsqldb.jdbcDriver</proxool:driver-class>
- <proxool:driver-properties>
- <proxool:property name="user" value="sa"/>
- <proxool:property name="password" value=""/>
- </proxool:driver-properties>
- <proxool:house-keeping-sleep-time>40000</proxool:house-keeping-sleep-time>
- <proxool:house-keeping-test-sql>select CURRENT_DATE</proxool:house-keeping-test-sql>
- <proxool:maximum-connection-count>10</proxool:maximum-connection-count>
- <proxool:minimum-connection-count>3</proxool:minimum-connection-count>
- <proxool:maximum-connection-lifetime>18000000</proxool:maximum-connection-lifetime> <!-- 5 hours -->
- <proxool:simultaneous-build-throttle>5</proxool:simultaneous-build-throttle>
- <proxool:recently-started-threshold>40000</proxool:recently-started-threshold>
- <proxool:overload-without-refusal-lifetime>50000</proxool:overload-without-refusal-lifetime>
- <proxool:maximum-active-time>60000</proxool:maximum-active-time>
- <proxool:verbose>true</proxool:verbose>
- <proxool:trace>true</proxool:trace>
- <proxool:fatal-sql-exception>Fatal error</proxool:fatal-sql-exception>
- <proxool:prototype-count>2</proxool:prototype-count>
- </proxool:proxool>
- </nothing-to-do-with-proxool>
- </something-else-entirely>
属性列表说明:
fatal-sql-exception: 它是一个逗号分割的信息片段.当一个SQL异常发生时,他的异常信息将与这个信息片段进行比较.如果在片段中存在,那么这个异常将被认为是个致命错误(Fatal SQL Exception ).这种情况下,数据库连接将要被放弃.无论发生什么,这个异常将会被重掷以提供给消费者.用户最好自己配置一个不同的异常来抛出.
fatal-sql-exception-wrapper-class:正如上面所说,你最好配置一个不同的异常来重掷.利用这个属性,用户可以包装SQLException,使他变成另外一个异常.这个异常或者继承SQLException或者继承字RuntimeException.proxool自带了2个实现:'org.logicalcobwebs.proxool.FatalSQLException' 和'org.logicalcobwebs.proxool.FatalRuntimeException' .后者更合适.
house-keeping-sleep-time: house keeper 保留线程处于睡眠状态的最长时间,house keeper 的职责就是检查各个连接的状态,并判断是否需要销毁或者创建.
house-keeping-test-sql: 如果发现了空闲的数据库连接.house keeper 将会用这个语句来测试.这个语句最好非常快的被执行.如果没有定义,测试过程将会被忽略。
injectable-connection-interface: 允许proxool实现被代理的connection对象的方法.
injectable-statement-interface: 允许proxool实现被代理的Statement 对象方法.
injectable-prepared-statement-interface: 允许proxool实现被代理的PreparedStatement 对象方法.
injectable-callable-statement-interface: 允许proxool实现被代理的CallableStatement 对象方法.
jmx: 略
jmx-agent-id: 略
jndi-name: 数据源的名称
maximum-active-time: 如果housekeeper 检测到某个线程的活动时间大于这个数值.它将会杀掉这个线程.所以确认一下你的服务器的带宽.然后定一个合适的值.默认是5分钟.
maximum-connection-count: 最大的数据库连接数.
maximum-connection-lifetime: 一个线程的最大寿命.
minimum-connection-count: 最小的数据库连接数
overload-without-refusal-lifetime: 略
prototype-count: 连接池中可用的连接数量.如果当前的连接池中的连接少于这个数值.新的连接将被建立(假设没有超过最大可用数).例如.我们有3个活动连接2个可用连接,而我们的prototype-count是4,那么数据库连接池将试图建立另外2个连接.这和 minimum-connection-count不同. minimum-connection-count把活动的连接也计算在内.prototype-count 是spare connections 的数量.
recently-started-threshold: 略
simultaneous-build-throttle: 略
statistics: 连接池使用状况统计。 参数“10s,1m,1d”
statistics-log-level: 日志统计跟踪类型。 参数“ERROR”或 “INFO”
test-before-use: 略
test-after-use: 略
trace: 如果为true,那么每个被执行的SQL语句将会在执行期被log记录(DEBUG LEVEL).你也可以注册一个ConnectionListener (参看ProxoolFacade)得到这些信息.
verbose: 详细信息设置。 参数 bool 值