熟悉Proxool连接池的朋友进来下！有个低级问题！

[boy_wh520]

jdbc-0.proxool.maximum-connection-count=20 （最大连接数）
jdbc-0.proxool.prototype-count=8 （初始化连接数）
jdbc-0.proxool.statistics=10s,1m,1d （这个是什么？）

还有请问 最小连接数，连接失效时间，应该怎么设置 时间是什么单位的！

[killme2008]

我们项目的设置:
<?xml version="1.0" encoding="utf-8"?>
<!-- the proxool configuration can be embedded within your own application's.
Anything outside the "proxool" tag is ignored.
For configuration features, please referred to http://proxool.sourceforge.net/future.html
-->
<something-else-entirely>
<proxool>
<alias>mzConPool</alias>
<!--proxool只能管理由自己产生的连接-->

<!-- mysql configuration -->

<driver-url>jdbc:mysql://192.168.8.110:3306/easyerp?useUnicode=true&characterEncoding=GB2312</driver-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<driver-properties>
<property name="user" value="root"/>
<property name="password" value=""/>
</driver-properties>




<!-- SqlServer configuration -->
<!--
<driver-url>jdbc:jtds:sqlserver://192.168.8.110:1433/easyerp;useUnicode=true&characterEncoding=GB2312;useCursors=true</driver-url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<driver-properties>
<property name="user" value="sa"/>
<property name="password" value="sa"/>
</driver-properties>
-->


<!-- How long the house keeping thread sleeps for (milliseconds). The house keeper is responsible for
checking the state of all the connections and tests whether any need to be destroyed or created.
Default is 30 seconds.
-->
<house-keeping-sleep-time>90000</house-keeping-sleep-time>

<!--If the house keeping thread finds and idle connections it will test them with this SQL statement.
It should be very quick to execute. Something like checking the current date or something.
If not defined then this test is omitted.
-->
<house-keeping-test-sql>select CURDATE()</house-keeping-test-sql>


<!--If the housekeeper comes across a thread that has been active for longer than this then it will kill it.
So make sure you set this to a number bigger than your slowest expected response.Default is 5 minutes-->
<maximum-active-time>50000</maximum-active-time>



<!-- The maximum number of connections to the database. Default is 15.-->
<maximum-connection-count>30</maximum-connection-count>

<!-- <maximum-connection-lifetime>
The maximum amount of time that a connection exists for before it is killed (milliseconds). Default is 4 hours.
-->


<!-- The minimum number of connections we will keep open, regardless of whether anyone needs them or not.
Default is 5.-->
<minimum-connection-count>10</minimum-connection-count>


<!-- If there are fewer than this number of connections available then we will build some more
(assuming the maximum-connection-count is not exceeded). For example.
Of we have 3 active connections and 2 available, but our prototype-count is 4 then it will attempt to build another 2.
This differs from minimum-connection-count because it takes into account the number of
active connections. minimum-connection-count is absolute and doesn't care how many are in use.
prototype-count is the number of spare connections it strives to keep over and above the ones that are
currently active. Default is 0.
-->
<prototype-count>5</prototype-count>



<!-- This is the maximum number of connections we can be building at any one time.
That is, the number of new connections that have been requested but aren't yet available for use.
Because connections can be built using more than one thread (for instance, when they are built on demand)
and it takes a finite time between deciding to build the connection and it becoming available we need some
way of ensuring that a lot of threads don't all decide to build a connection at once.
(We could solve this in a smarter way - and indeed we will one day) Default is 10.
-->
<simultaneous-build-throttle>10</simultaneous-build-throttle>

</proxool>
</something-else-entirely>

[boy_wh520]

能否简短些！