4 Types of configuration data sources in spring (GO)

Original http://blog.csdn.net/orclight/article/details/8616103

Regardless of which persistence technology is used, you need to define a data source. There are 4 different forms of data source configuration available in spring:

Spring comes with a data source (Drivermanagerdatasource), a DBCP data source, a C3P0 data source, and a jndi data source.

1.spring of your own data source

Drivermanagerdatasource

XML code:

[HTML]View Plaincopy

2. <Bean id="DataSource"
4. class="Org.springframework.jdbc.datasource.DriverManagerDataSource">
6. <property name= "driverclassname" value="Oracle.jdbc.driver.OracleDriver" />
8. <property name="url" value="JDBC:ORACLE:THIN:@172.19.34.6:1521:ORCL" />
10. <property name= "username" value="orclight" />
12. <property name= "password" value="123456" />
14. </Bean>

2.DBCP Data source

The configuration of the dbcp depends on the 2 jar package Commons-dbcp.jar,commons-pool.jar.

XML code:

[HTML]View Plaincopy

2. <Bean id= "dataSource" class="Org.apache.commons.dbcp.BasicDataSource "
4. destroy-method="Close">
6. <property name= "driverclassname" value="Oracle.jdbc.driver.OracleDriver" />
8. <property name="url" value="JDBC:ORACLE:THIN:@172.19.34.6:1521:ORCL" />
10. <property name= "username" value="orclight" />
12. <property name= "password" value="123456" />
14. </Bean>

Explanation of the above code:

Basicdatasource provides the close () method to turn off the data source, so you must set the destroy-method= "close" property so that the data source shuts down gracefully when the spring container is closed. In addition to the data source properties that are required above, there are some common properties:
Defaultautocommit: Sets whether the connection returned from the data source takes the auto-commit mechanism, and the default value is true;
Defaultreadonly: Sets whether the data source can only perform read-only operations, the default value is false;
Maxactive: Maximum Connection database connection number, set to 0 o'clock, indicating no limit;
Maxidle: The maximum number of waiting connections, set to 0 o'clock, indicates no limit;
Maxwait: The maximum number of seconds to wait, in milliseconds, over time will be reported error message;
Validationquery: A query SQL statement that verifies that a connection is successful, the SQL statement must return at least one row of data, as you can simply set to: "SELECT COUNT (*) from user";
Removeabandoned: Whether self-interruption, default is false;
Removeabandonedtimeout: The data connection is automatically disconnected after a few seconds, and the value is provided when removeabandoned is true;
Logabandoned: If the interrupt event is logged, the default is false;

3.C3P0 Data source

C3P0 is an open source JDBC data source implementation project, C3P0 relies on the jar package C3p0.jar.

XML code:

[HTML]View Plaincopy

2. <Bean id= "dataSource" class="Com.mchange.v2.c3p0.ComboPooledDataSource "
4. destroy-method="Close">
6. <property name= "driverclass" value="oracle.jdbc.driver.OracleDriver"/>
8. <property name= "jdbcurl" value="JDBC:ORACLE:THIN:@172.19.34.6:1521:ORCL"/>
10. <property name="user" value="orclight"/>
12. <property name= "password" value="123456"/>
14. </Bean>

Combopooleddatasource and Basicdatasource provide a close () method for shutting down the data source so that we can guarantee that the data source will be released successfully when the spring container is closed.

C3P0 has richer configuration properties than DBCP, which allow for a variety of effective control over the data source:
Acquireincrement: When a connection in the connection pool is exhausted, C3P0 creates the number of new connections at once;
Acquireretryattempts: Defines the number of repeated attempts to obtain a new connection from the database after a failure, default is 30;
Acquireretrydelay: Two times the interval in the connection, in milliseconds, the default is 1000;
Autocommitonclose: All uncommitted operations are rolled back by default when the connection is closed. The default is false;
AUTOMATICTESTTABLE:C3P0 will build an empty table named Test and test it with its own query statement. If this parameter is defined, then the property preferredtestquery is ignored. You cannot take any action on this test table, it will be used in the C3P0 test, default is null;
Breakafteracquirefailure: Getting a connection failure will cause all threads waiting to get the connection to throw an exception. However, the data source is still valid and continues to try to get the connection the next time you call Getconnection (). If set to True, the data source will declare broken and permanently shut down after attempting to acquire a connection failure. The default is false;
Checkouttimeout: When the connection pool is exhausted, the client calls getconnection () to wait for a new connection, and then throws SqlException after the timeout, and waits indefinitely if set to 0. Unit milliseconds, default is 0;
Connectiontesterclassname: To test a connection by implementing a class of Connectiontester or Queryconnectiontester, the class name needs to be set to the fully qualified name. The default is Com.mchange.v2.C3P0.impl.DefaultConnectionTester;
Idleconnectiontestperiod: How many seconds to check the idle connection in all connection pools, the default is 0 means no check;
Initialpoolsize: The number of connections created at initialization should be taken between Minpoolsize and Maxpoolsize. The default is 3;
MaxIdleTime: Maximum idle time, the connection over idle time will be discarded. 0 or negative numbers will never be discarded. The default is 0;
Maxpoolsize: The maximum number of connections that are kept in the connection pool. The default is 15;
MAXSTATEMENTS:JDBC standard parameter to control the number of PreparedStatement loaded within the data source. However, because the pre-cached statement belong to a single connection instead of the entire connection pool. So setting this parameter takes many factors into account, and if both maxstatements and maxstatementsperconnection are 0, the cache is closed. The default is 0;
Maxstatementsperconnection: The maximum number of cache statement that a single connection in a connection pool has. The default is 0;
NUMHELPERTHREADS:C3P0 are asynchronous operations, and slow JDBC operations are done by helping the process. Extending these operations can effectively improve performance, and multiple operations are performed simultaneously through multithreading. The default is 3;
Preferredtestquery: Defines test statements that are executed by all connection tests. This parameter can significantly improve the test speed when using the connection test. The test table must exist at the time of the initial data source. default is null;
Propertycycle: The maximum number of seconds a user waits before modifying system configuration parameters. The default is 300;
Testconnectiononcheckout: Please use it only when you need it because of high performance consumption. If set to true then the validity of each connection submission is officer. It is recommended to use Idleconnectiontestperiod or automatictesttable
and other methods to improve the performance of the connection test. The default is false;
Testconnectiononcheckin: If set to true then the validity of the officer connection is obtained while the connection is made. The default is False.

4.JNDI Data source

If the application is configured on a high-performance application server, such as WebLogic or websphere,tomcat, we may prefer to use the data source provided by the application server itself. The data source for the application server is used by Jndi open callers, and spring specifically provides the Jndiobjectfactorybean class that references the Jndi resource.

XML code:

[HTML]View Plaincopy

1. <Bean id= "dataSource" class="Org.springframework.jndi.JndiObjectFactoryBean">
2. <property name= "jndiname" value="java:comp/env/jdbc/orclight"/>
3. </Bean>

[HTML]View Plaincopy

2. <beans xmlns=http://www.springframework.org/schema/beans
4. xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
6. xmlns:jee=Http://www.springframework.org/schema/jee
8. Xsi:schemalocation= "Http://www.springframework.org/schema/beans
10. Http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
12. Http://www.springframework.org/schema/jee
14. Http://www.springframework.org/schema/jee/spring-jee-2.0.xsd ">
16. <jee:jndi-lookup id="DataSource" jndi-name="java:comp/env/jdbc/orclight"/>
18. </Beans>

Reference article:

1.Spring configuration Data Source Four ways http://www.2cto.com/kf/201301/184061.html

2. Configure the spring data source http://www.cnblogs.com/200911/archive/2012/08/10/2631760.html

3.Spring Multi-Data Source configuration method http://blog.csdn.net/nickbest85/article/details/5510466

4. How to solve problems with multiple data sources in the spring framework http://www.iteye.com/topic/72486

4 Types of configuration data sources in spring (GO)