2.spring中配置proxool數據源

時間 2019-11-24

標籤 2.spring spring 配置 proxool 數據欄目 Spring 简体版

原文原文鏈接

方式一：
在Spring的"applicationContext.xml"中的dataSource bean定義——java

 1 <bean id="dataSource"
 2     class="org.logicalcobwebs.proxool.ProxoolDataSource">
 3     <property name="driver">
 4         <value>com.mysql.jdbc.Driver</value>
 5     </property>
 6     <property name="driverUrl">
 7         <value>jdbc:mysql://localhost:3306/dbname?user=yourname&amp;password=yourpass</value>
 8     </property>
 9     <property name="user" value="yourname" />
10     <property name="password" value="yourpass" />
11     <property name="alias" value="Pool_dbname" />
12     <property name="houseKeepingSleepTime" value="90000" />
13     <property name="prototypeCount" value="0" />
14     <property name="maximumConnectionCount" value="50" />
15     <property name="minimumConnectionCount" value="2" />
16     <property name="simultaneousBuildThrottle" value="50" />
17     <property name="maximumConnectionLifetime" value="14400000" />
18     <property name="houseKeepingTestSql" value="select CURRENT_DATE" />
19 </bean>

第一種方式須要把用戶名和密碼寫在鏈接串裏面，
ProxoolDataSource類提供的user，password屬性彷佛沒有什麼用。
不管提供什麼，它都會以空用戶名、密碼去鏈接數據庫。
這多是Proxool RC0.93的一個bug，實在讓人惱火，不知道最新的0.9.1有沒有fix這個bug。
不過配置中的user，password兩個屬性還必須設置，不然hibernate會報空指針錯誤。mysql

方式二：
在Spring的"applicationContext.xml"中的dataSource bean定義——web

1 <bean id="dataSource"
2     class="org.springframework.jdbc.datasource.DriverManagerDataSource">
3     <property name="driverClassName">
4         <value>org.logicalcobwebs.proxool.ProxoolDriver</value>
5     </property>
6     <property name="url">
7         <value>proxool.Pool_dbname</value>
8     </property>
9 </bean>

第二種方式須要預先在"web.xml"先配置好Proxool鏈接池，配置以下：spring

 1 <servlet>
 2     <servlet-name>proxoolServletConfigurator</servlet-name>
 3     <servlet-class>
 4         org.logicalcobwebs.proxool.configuration.ServletConfigurator
 5     </servlet-class>
 6     <init-param>
 7         <param-name>xmlFile</param-name>
 8         <param-value>WEB-INF/proxool.xml</param-value>
 9     </init-param>
10     <load-on-startup>1</load-on-startup>
11 </servlet>
12 
13 <servlet>
14     <servlet-name>context</servlet-name>
15     <servlet-class>
16         org.springframework.web.context.ContextLoaderServlet
17     </servlet-class>
18     <load-on-startup>2</load-on-startup>
19 </servlet>

注意，第二種方式下Spring的上下文加載若是想使用listener方式(Struts2要求)，
則與鏈接池有關的Bean全得延遲初始化。由於listener比servlet優先初始化，
若是相關Bean不是lazy-init的話，則啓動服務器時會出現Bean找不到鏈接定義的異常。sql

1  <listener>
2   <listener-class>
3       org.springframework.web.context.ContextLoaderListener
4   </listener-class>
5  </listener>

其中proxool的配置文件能夠採用xmlFile"proxool.xml"或者propertyFile"proxool.properties"數據庫

"proxool.xml"格式以下：服務器

 1 <?xml version="1.0" encoding="UTF-8"?>
 2 <proxool-config>
 3    <proxool>
 4       <alias>Pool_dbname</alias>
 5       <driver-url>jdbc:mysql://localhost:3306/dbname</driver-url>
 6       <driver-class>com.mysql.jdbc.Driver</driver-class>
 7       <driver-properties>
 8       <property name="user" value="yourname"/>
 9       <property name="password" value="yourpass"/>
10       </driver-properties>
11       <house-keeping-sleep-time>60000</house-keeping-sleep-time>
12       <maximum-connection-count>20</maximum-connection-count>　
13       <minimum-connection-count>2</minimum-connection-count>
14       <prototype-count>0</prototype-count>
15       <simultaneous-build-throttle>20</simultaneous-build-throttle>
16       <house-keeping-test-sql>select CURRENT_DATE</house-keeping-test-sql>
17       <statistics>15s,10m,1d</statistics>
18       <statistics-log-level>INFO</statistics-log-level>
19    </proxool>
20    <proxool>
21     <!--能夠配置多個庫-->
22    </proxool>
23 </proxool-config>

"proxool.properties"格式以下：app

 1 jdbc-0.proxool.alias=Pool_dbname
 2 jdbc-0.proxool.driver-url=jdbc:mysql://localhost:3306/dbname
 3 jdbc-0.proxool.driver-class=com.mysql.jdbc.Driver
 4 jdbc-0.user=yourname
 5 jdbc-0.password=yourpass
 6 jdbc-0.proxool.house-keeping-sleep-time=60000
 7 jdbc-0.proxool.house-keeping-test-sql=select CURRENT_DATE
 8 jdbc-0.proxool.maximum-connection-count=10
 9 jdbc-0.proxool.minimum-connection-count=3
10 jdbc-0.proxool.maximum-connection-lifetime=18000000
11 jdbc-0.proxool.prototype-count=3
12 jdbc-0.proxool.simultaneous-build-throttle=10
13 jdbc-0.proxool.recently-started-threshold=60000
14 jdbc-0.proxool.overload-without-refusal-lifetime=50000
15 jdbc-0.proxool.maximum-active-time=60000
16 jdbc-0.proxool.verbose=true
17 jdbc-0.proxool.trace=true
18 jdbc-0.proxool.fatal-sql-exception=Fatal error
19 
20 jdbc-2.proxool.alias=Pool_dbname2
21 ……
22 <!--能夠配置多個庫-->
23

3、更詳細的proxool.xml的配置屬性說明:
jsp

Xml代碼

 1 <?xml version="1.0" encoding="ISO-8859-1"?><!--  
 2 Properties for Proxool Configurator testing. Defines the same parameters as  
 3 TestHelper.buildCompleteAlternativeProperties()  
 4 -->  
 5 <something-else-entirely xmlns="http://sumthin.else.entirely" xmlns:proxool="The latest version is available at http://proxool.sourceforge.net/xml-namespace">  
 6     <proxool:proxool>  
 7         <proxool:alias>xml-test-ns</proxool:alias>  
 8         <proxool:driver-url>jdbc:hsqldb:db/test</proxool:driver-url>  
 9         <proxool:driver-class>org.hsqldb.jdbcDriver</proxool:driver-class>  
10         <proxool:driver-properties>  
11             <proxool:property name="user" value="sa"/>  
12             <proxool:property name="password" value=""/>  
13         </proxool:driver-properties>  
14         <proxool:house-keeping-sleep-time>40000</proxool:house-keeping-sleep-time>  
15         <proxool:house-keeping-test-sql>select CURRENT_DATE</proxool:house-keeping-test-sql>  
16         <proxool:maximum-connection-count>10</proxool:maximum-connection-count>  
17         <proxool:minimum-connection-count>3</proxool:minimum-connection-count>  
18         <proxool:maximum-connection-lifetime>18000000</proxool:maximum-connection-lifetime> <!-- 5 hours -->  
19         <proxool:simultaneous-build-throttle>5</proxool:simultaneous-build-throttle>  
20         <proxool:recently-started-threshold>40000</proxool:recently-started-threshold>  
21         <proxool:overload-without-refusal-lifetime>50000</proxool:overload-without-refusal-lifetime>  
22         <proxool:maximum-active-time>60000</proxool:maximum-active-time>  
23         <proxool:verbose>true</proxool:verbose>  
24         <proxool:trace>true</proxool:trace>  
25         <proxool:fatal-sql-exception>Fatal error</proxool:fatal-sql-exception>  
26         <proxool:prototype-count>2</proxool:prototype-count>  
27     </proxool:proxool>  
28     <nothing-to-do-with-proxool>  
29         <proxool:proxool>  
30             <proxool:alias>xml-test-ns-2</proxool:alias>  
31             <proxool:driver-url>jdbc:hsqldb:db/test</proxool:driver-url>  
32             <proxool:driver-class>org.hsqldb.jdbcDriver</proxool:driver-class>  
33             <proxool:driver-properties>  
34                 <proxool:property name="user" value="sa"/>  
35                 <proxool:property name="password" value=""/>  
36             </proxool:driver-properties>  
37             <proxool:house-keeping-sleep-time>40000</proxool:house-keeping-sleep-time>  
38             <proxool:house-keeping-test-sql>select CURRENT_DATE</proxool:house-keeping-test-sql>  
39             <proxool:maximum-connection-count>10</proxool:maximum-connection-count>  
40             <proxool:minimum-connection-count>3</proxool:minimum-connection-count>  
41             <proxool:maximum-connection-lifetime>18000000</proxool:maximum-connection-lifetime> <!-- 5 hours -->  
42             <proxool:simultaneous-build-throttle>5</proxool:simultaneous-build-throttle>  
43             <proxool:recently-started-threshold>40000</proxool:recently-started-threshold>  
44             <proxool:overload-without-refusal-lifetime>50000</proxool:overload-without-refusal-lifetime>  
45             <proxool:maximum-active-time>60000</proxool:maximum-active-time>  
46             <proxool:verbose>true</proxool:verbose>  
47             <proxool:trace>true</proxool:trace>  
48             <proxool:fatal-sql-exception>Fatal error</proxool:fatal-sql-exception>  
49             <proxool:prototype-count>2</proxool:prototype-count>  
50         </proxool:proxool>  
51     </nothing-to-do-with-proxool>  
52 </something-else-entirely>  
53

屬性列表說明:測試

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 值

4、還能夠配置管理proxool的servlet

Xml代碼

 1 <?xml version="1.0" encoding="UTF-8"?>  
 2 <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"  
 3     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
 4     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee   
 5     http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">  
 6 <servlet>  
 7   <servlet-name>ServletConfigurator</servlet-name>  
 8   <servlet-class>  
 9     org.logicalcobwebs.proxool.configuration.ServletConfigurator  
10   </servlet-class>  
11   <init-param>  
12     <param-name>xmlFile</param-name>  
13     <param-value>WEB-INF/proxool.xml</param-value>  
14   </init-param>  
15   <load-on-startup>1</load-on-startup>  
16 </servlet>  
17   
18 <servlet>  
19   <servlet-name>Admin</servlet-name>  
20   <servlet-class>  
21     org.logicalcobwebs.proxool.admin.servlet.AdminServlet  
22   </servlet-class>  
23 </servlet>  
24 <servlet-mapping>  
25   <servlet-name>Admin</servlet-name>  
26   <url-pattern>/admin</url-pattern>  
27 </servlet-mapping>  
28 <!-- 配置受保護域，只有Tomcat管理員才能察看鏈接池的信息 -->  
29 <security-constraint>  
30   <web-resource-collection>  
31       <web-resource-name>proxool</web-resource-name>   
32       <url-pattern>/admin</url-pattern>  
33   </web-resource-collection>  
34   <auth-constraint>  
35      <role-name>manager</role-name>   
36      </auth-constraint>  
37   </security-constraint>  
38  <login-config>  
39      <auth-method>BASIC</auth-method>   
40      <realm-name>proxool manager Application</realm-name>   
41   </login-config>  
42   <security-role>  
43     <description>The role that is required to log in to the Manager Application</description>   
44      <role-name>manager</role-name>   
45  </security-role>  
46   <error-page>  
47     <error-code>401</error-code>  
48     <location>/401.jsp</location>  
49   </error-page>  
50 </web-app>