Proxool Connection Pool

Today configuration Proxool Connection pool, found the configurable properties are very much, used to be only used, did not summarize, today checked the next online information, summed up

Convenient for you and me. In fact, many of the online English materials are very full, online a lot of people are test translation of foreign articles to earn some traffic, in fact, no meaning, programming play, translation

It doesn't mean anything to say what you are. I am also translating a document today:

Property List Description:

fatal-sql-exception: It is a comma-delimited piece of information. When an SQL exception occurs, his exception information is compared to this fragment of information. If

exists in the fragment, the exception is considered a fatal error (Fatal SQL Exception). In this case, the database connection will be discarded. No matter what happens

, the exception will be re-thrown to provide the consumer. It is best for the user to configure a different exception to throw.

Fatal-sql-exception-wrapper-class: As mentioned above, you'd better configure a different exception to re-throw. With this attribute, users can package

SQLException, making him another exception. This exception either inherits SQLException or inherits the word RuntimeException. Proxool

Comes with 2 implementations: ' Org.logicalcobwebs. Proxool. Fatalsqlexception ' and ' Org.logicalcobwebs. Proxool. Fatalruntimeexception '

. The latter is more appropriate.

House-keeping-sleep-time:house keeper retains the maximum time the thread is asleep, house keeper's job is to check

The status of each connection and determine whether it needs to be destroyed or created.

House-keeping-test-sql: If an idle database connection is found. House keeper will use this statement to test. This statement is best not

is executed frequently. If there is no definition, the test process will be ignored.

injectable-connection-interface: A method that allows Proxool to implement the connection object being proxied.

injectable-statement-interface: allows Proxool to implement the statement object method being proxied.

injectable-prepared-statement-interface: allows Proxool to implement the PreparedStatement object method being proxied.

injectable-callable-statement-interface: allows Proxool to implement the CallableStatement object method being proxied.

JMX: If the property is true, a message bean is registered to the JMS service, the message Bean object name: "Proxool:type=pool, name=<alias>". The default value is False.

Jmx-agent-id: A comma-delimited list of JMX proxies, such as connection pools registered with Mbeanserverfactory.findmbeanserver (String agentid). ）

This property is valid only if the "JMX" property is set to "true". All registered JMX servers use this property to be indeterminate

jndi-name: name of the data source

maximum-active-time: If housekeeper detects that the active time of a thread is greater than this number. It will kill this thread.

So check the bandwidth of your server. Then set a suitable value. The default is 5 minutes.

maximum-connection-count: Maximum number of database connections.

maximum-connection-lifetime: The maximum lifespan of a thread.

minimum-connection-count: minimum number of database connections

Overload-without-refusal-lifetime: This can help us determine the status of the connection pool. If we have rejected a connection at this SetPoint

(milliseconds) and is then considered overloaded. The default is 60 seconds.

prototype-count: The number of connections available in the connection pool. If the connection in the current connection pool is less than this value. New connections will be built

(assuming no more than the maximum available number). For example, we have 3 active connections with 2 available connections, and our prototype-count is 4, so number

The library connection pool will attempt to establish an additional 2 connections. This is different from Minimum-connection-count. Minimum-connection-count

The connection to the activity is also counted. Prototype-count is the number of spare connections.

Recently-started-threshold: This can help us determine the state of the connection pool, whether the number of connections is few or more or overloaded. As long as there is at least one connection

Has started in this value (MS), or there are some extra available connections, we assume that the connection pool is open. Default is 60 seconds

simultaneous-build-throttle: This is the maximum number of connections we can make at one time. That is the new connection request, but there is no connection available. Because

A connection can use multiple threads to establish a connection between a limited amount of time to bring in a usable link, but we need some way to confirm that some threads are not responding immediately

The default is 10 for connection requests.

Statistics: Connection Pool usage statistics. Parameter "10s,1m,1d"

statistics-log-level: log Statistics trace type. Parameter "ERROR" or "INFO"

Test-before-use: If True, the connection is serviced before each connection is tested, and if one fails, it is discarded and the other connection is

is processed, if all connections fail, a new connection will be established. Otherwise, a SqlException exception will be thrown.

Test-after-use: If True, the connection will be serviced after each connection has been tested, returning it to the connection pool and discarded if the connection fails.

Trace: If true, then each executed SQL statement will be logged at the execution time (DEBUG level). You can also register a connectionlistener (see Proxoolfacade) to get this information .

verbose: details settings. parameter bool Value

Proxool Connection Pool