Jboss Data Source Configuration parameters

Jndi: Specify Jndi name for data source

is enabled: Specifies whether the data source should be started. Note: Runtime support for this property is not available in the next release.

Statistics Enabled: Defines whether to enable runtime statistics.

Datasource CLASS:JDBC The fully qualified name of the data source class

Driver: Defines the JDBC driver that the data source should use. This is a symbol name that matches the installed driver. If the driver is deployed as a JAR, then this name is the name of the deployment unit.

Fully qualified name of the Driver Class:jdbc driver class

Share Prepared Statements: whether to share the Prepared statement, that is, whether to request the same statement two times without shutting down the use of the same underlying Prepared statement.

Statement Cache Size:lru The number of prepared statements in each connection.

Connection URL:JDBC Driver Connection URL

New Connection sql: Specifies the SQL statement to execute whenever a connection is added to the connection pool

Transaction Isolation: Sets the transaction isolation level for the Java.sql.Connection. Valid values are: transaction_read_uncommitted, transaction_read_committed, Transaction_repeatable_read, TRANSACTION_ SERIALIZABLE and Transaction_none

Use JTA: Enable JTA integration

Use CCM: Enable cache Connection Manager usage

Min Pool size:min-pool-size element specifies the minimum number of connections in the pool the max pool size:max-pool-size element specifies the maximum number of connections in the pool. No more connections can be created in each sub-pool.

Strict Minimum: Specifies whether the min-pool-size should be treated strictly

Prefill enabled: Whether the connection pool should be pre-populated. You can modify this value only on a disabled data source, or you will need to restart the server.

Flush Strategy: Specifies how the connection pool clears when an error is encountered. Valid values are: failingconnectiononly (default), Idleconnections, and Entirepool.

The idle timeout:idle-timeout-minutes element specifies the maximum time (in minutes) that a connection can remain idle before it is closed. The actual maximum time is also dependent on the Idleremover scan time, which is half the minimum idle-timeout-minutes of the pool. You can only modify this value on a disabled data source, or you will need to restart the server.

Track Statements: Checks if the statement is not closed when the connection is returned to the connection dominant, the result set is closed, the statement is closed, or is returned to the prepared statement cache. Valid values are: "false"-do not Track statements, "true"-trace statements and result sets and warn when no close is issued, "nowarn"-Trace statements but do not warn when not closed.

Username: Specifies the user name to use when creating a new connection Password: Specifies the password to use when creating a new connection

Security Domain: Specifies the secure domains that define the javax.security.auth.Subject used to differentiate connections in the pool

PROPERTIES:JDBC Connection Properties

Valid Connection Checker:org.jboss.jca.adapters.jdbc.ValidConnectionChecker offers a isvalidconnection (Connection) method to verify the connection. If a throw exception is returned, the connection is invalid. This covers the Check-valid-connection-sql element.

Check Valid sql: Specifies an SQL statement to check the validity of a pooled connection. It may be called when a managed connection is obtained from this pool.

The Validate on Match:validate-on-match element Specifies whether connection validation occurs when the connection factory attempts to match a managed connection. This is usually mutually exclusive with the background test.

Background Validation: This element specifies whether the connection should be checked on the background thread or before it is used. You can only modify this value on a disabled data source, or you will need to restart the server.

The Validation millis:background-validation-millis element specifies the time, in milliseconds, that the background validation will run. You can only modify this value on a disabled data source, or you will need to restart the server.

Stale Connection Checker: Provides the Isstaleconnection (SQLException) method Org.jboss.jca.adapters.jdbc.StaleConnectionChecker, if it returns true, wraps the exception in the In the org.jboss.jca.adapters.jdbc.StaleConnectionException.

Exception Sorter:org.jboss.jca.adapters.jdbc.ExceptionSorter provides a isexceptionfatal (SQLException) method to verify whether an exception should broadcast an error

Use Trylock (): Timeout period for internal locks on resource adapter objects (seconds)

The Blocking Timeout millis:blocking-timeout-millis element specifies the blocking time (in milliseconds) to wait for a connection before throwing an exception. Note that this only blocks when waiting to lock the connection, and does not throw an exception if it takes a very long time to create a new connection.

The idle Timeout minutes:idle-timeout-minutes element specifies the maximum time (in minutes) that a connection can remain idle before it is closed. The actual maximum time is also dependent on the Idleremover scan time, which is half the minimum idle-timeout-minutes of the pool. You can only modify this value on a disabled data source, or you will need to restart the server.

Set TX query timeout: Sets the query time-out based on the remaining time unit until the transaction supermarket. If there is no transaction, any configured query time-outs will be used.

Query Timeout: Configures the queue time-out (in seconds). If not specified, there is no time-out.

Allocation retry:allocation Retry element specifies the number of times the connection should be attempted before an exception is thrown

Allocation Retry wait millis:allocation Retry wait Millis element specifies the time (in milliseconds) to wait before attempting to allocate a connection