urn:jboss:domain:datasources:5.0

[ The min-pool-size element indicates the minimum number of connections a pool should hold. These are not created until a Subject is known from a request for a connection. This default to 0. Ex: <min-pool-size>1</min-pool-size>

[ The initial-pool-size element indicates the initial number of connections a pool should hold. This default to 0. Ex: <initial-pool-size>1</initial-pool-size>

[ The max-pool-size element indicates the maximum number of connections for a pool. No more connections will be created in each sub-pool. This defaults to 20.

[ Whether to attempt to prefill the connection pool. Empty element denotes a true value. e.g. <prefill>true</prefill>. Default is false

[ Defines if pool use should be fair Default true

[ Define if the min-pool-size should be considered a strictly. Default false

[ Specifies how the pool should be flush in case of an error. Valid values are: FailingConnectionOnly (default), InvalidIdleConnections, IdleConnections, Gracefully, EntirePool, AllInvalidIdleConnections, AllIdleConnections, AllGracefully, AllConnections

[ Specifies if multiple users will access the datasource through the getConnection(user, password) method and hence if the internal pool type should account for that

[ Specifies the capacity policies for the pool

[ An org.jboss.jca.adapters.jdbc.spi.listener.ConnectionListener that provides a possible to listen for connection activation and passivation in order to perform actions before the connection is returned to the application or returned to the pool. Ex: <connection-listener class-name="com.acme.jdbc.OracleConnectionListener"/>

Name	Type	Default	Description
class-name	token

[ Specify the username used when creating a new connection. Ex: <user-name>sa</user-name>

[ Specify the password used when creating a new connection. Ex: <password>sa-pass</password>

Credential to be used by the configuration.

Name	Type	Default	Description
clear-text	string		Credential/password in clear text. Use just for testing purpose. Otherwise use credential store to mask the actual credential from your configuration.

[ Indicates Subject (from security domain) are used to distinguish connections in the pool. The content of the security-domain is the name of the JAAS security manager that will handle authentication. This name correlates to the JAAS login-config.xml descriptor application-policy/name attribute. Ex: <security-domain>HsqlDbRealm</security-domain>

[ Indicates that Elytron is responsible for authenticating connections. If authentication-context is configured (via authentication-context), Elytron will use the specified context for authenticating. Else, Elytron will use the current authentication context of the caller that is retrieving the connection. Ex: <elytron-enabled/>

[ Indicates the Elytron context that will be used for authenticating connections during container-managed sign-on. The resulting Subject will be used to distinguish connections in the pool. The authentication-context name correlates to the authentication context defined in the Elytron subsystem. Ex: <elytron-enabled/> <authentication-context>HsqlDbContext</authentication-context>

Name	Type	Default	Description
class-name	token

[ An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides a SQLException isValidConnection(Connection e) method to validate is a connection is valid. An exception means the connection is destroyed. This overrides the check-valid-connection-sql when present. Ex: <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleValidConnectionChecker"/>

Name	Type	Default	Description
class-name	token

[ Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.

[ The validate-on-match element indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set. This is typically exclusive to the use of background validation

[ An element to specify that connections should be validated on a background thread versus being validated prior to use

[ The background-validation-millis element specifies the amount of time, in millis, that background validation will run.

[ Whether fail a connection allocation on the first connection if it is invalid (true) or keep trying until the pool is exhausted of all potential connections (false) default false. e.g. <use-fast-fail>true</use-fast-fail>

[ An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides a boolean isStaleConnection(SQLException e) method which if it it returns true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException which is a subclass of SQLException. Ex: <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleStaleConnectionChecker"/>

Name	Type	Default	Description
class-name	token

[ An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides a boolean isExceptionFatal(SQLException e) method to validate is an exception should be broadcast to all javax.resource.spi.ConnectionEventListener as a connectionErrorOccurred message. Ex: <exception-sorter class-name="org.jboss.jca.adapters.jdbc.vendor.OracleExceptionSorter"/>

Name	Type	Default	Description
class-name	token

[ The blocking-timeout-millis element indicates the maximum time in milliseconds to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for a permit for a connection, and will never throw an exception if creating a new connection takes an inordinately long time. The default is 30000 (30 seconds).

[ The idle-timeout-minutes elements indicates the maximum time in minutes a connection may be idle before being closed. The actual maximum time depends also on the IdleRemover scan time, which is 1/2 the smallest idle-timeout-minutes of any pool.

[ Whether to set the query timeout based on the time remaining until transaction timeout, any configured query timeout will be used if there is no transaction. The default is false. e.g. <set-tx-query-timeout/>

[ Any configured query timeout in seconds The default is no timeout e.g. 5 minutes <query-timeout>300</query-timeout>

[ Any configured timeout for internal locks on the resource adapter objects in seconds The default is a 60 second timeout e.g. 5 minutes <use-try-lock>300</use-try-lock>

[ The allocation retry element indicates the number of times that allocating a connection should be tried before throwing an exception. The default is 0.

[ The allocation retry wait millis element indicates the time in milliseconds to wait between retrying to allocate a connection. The default is 5000 (5 seconds).

[ Passed to XAResource.setTransactionTimeout() Default is zero which does not invoke the setter. In seconds e.g. 5 minutes <xa-resource-timeout>300</xa-resource-timeout>

[ Whether to check for unclosed statements when a connection is returned to the pool and result sets are closed when a statement is closed/return to the prepared statement cache. valid values are: false - do not track statements and results true - track statements and result sets and warn when they are not closed nowarn - track statements but do no warn about them being unclosed (the default) e.g. <track-statements>nowarn</track-statements>

[ The number of prepared statements per connection in an LRU cache

[ Whether to share prepare statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement. The default is false. e.g. <share-prepared-statements/>

[ The is-same-rm-override element allows one to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns true or false. Ex: <is-same-rm-override>true</is-same-rm-override>

[ An element to enable interleaving for XA connection factories Ex: <interleaving/>

[ Oracle does not like XA connections getting used both inside and outside a JTA transaction. To workaround the problem you can create separate sub-pools for the different contexts using <no-tx-separate-pools/> Ex: <no-tx-separate-pools/>

[ Should the Xid be padded Ex: <pad-xid>true</pad-xid>

[ Should the XAResource instances be wrapped in an org.jboss.tm.XAResourceWrapper instance Ex: <wrap-xa-resource>true</wrap-xa-resource>

[ Specify the username used when creating a new connection. Ex: <user-name>sa</user-name>

[ Specify the password used when creating a new connection. Ex: <password>sa-pass</password>

Credential to be used by the configuration.

Name	Type	Default	Description
clear-text	string		Credential/password in clear text. Use just for testing purpose. Otherwise use credential store to mask the actual credential from your configuration.

[ Indicates Subject (from security domain) are used to distinguish connections in the pool. The content of the security-domain is the name of the JAAS security manager that will handle authentication. This name correlates to the JAAS login-config.xml descriptor application-policy/name attribute. Ex: <security-domain>HsqlDbRealm</security-domain>

[ Indicates that Elytron is responsible for authenticating connections. If authentication-context is configured (via authentication-context), Elytron will use the specified context for authenticating. Else, Elytron will use the current authentication context of the caller that is retrieving the connection. Ex: <elytron-enabled/>

[ Indicates the Elytron context that will be used for authenticating connections during container-managed sign-on. The resulting Subject will be used to distinguish connections in the pool. The authentication-context name correlates to the authentication context defined in the Elytron subsystem. Ex: <elytron-enabled/> <authentication-context>HsqlDbContext</authentication-context>

Name	Type	Default	Description
class-name	token

[ An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides a SQLException isValidConnection(Connection e) method to validate is a connection is valid. An exception means the connection is destroyed. This overrides the check-valid-connection-sql when present. Ex: <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleValidConnectionChecker"/>

Name	Type	Default	Description
class-name	token

[ Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.

[ The validate-on-match element indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set. This is typically exclusive to the use of background validation

[ An element to specify that connections should be validated on a background thread versus being validated prior to use

[ The background-validation-millis element specifies the amount of time, in millis, that background validation will run.

[ Whether fail a connection allocation on the first connection if it is invalid (true) or keep trying until the pool is exhausted of all potential connections (false) default false. e.g. <use-fast-fail>true</use-fast-fail>

[ An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides a boolean isStaleConnection(SQLException e) method which if it it returns true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException which is a subclass of SQLException. Ex: <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.vendor.OracleStaleConnectionChecker"/>

Name	Type	Default	Description
class-name	token

[ An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides a boolean isExceptionFatal(SQLException e) method to validate is an exception should be broadcast to all javax.resource.spi.ConnectionEventListener as a connectionErrorOccurred message. Ex: <exception-sorter class-name="org.jboss.jca.adapters.jdbc.vendor.OracleExceptionSorter"/>

Name	Type	Default	Description
class-name	token

[ The blocking-timeout-millis element indicates the maximum time in milliseconds to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for a permit for a connection, and will never throw an exception if creating a new connection takes an inordinately long time. The default is 30000 (30 seconds).

[ The idle-timeout-minutes elements indicates the maximum time in minutes a connection may be idle before being closed. The actual maximum time depends also on the IdleRemover scan time, which is 1/2 the smallest idle-timeout-minutes of any pool.

[ Whether to set the query timeout based on the time remaining until transaction timeout, any configured query timeout will be used if there is no transaction. The default is false. e.g. <set-tx-query-timeout/>

[ Any configured query timeout in seconds The default is no timeout e.g. 5 minutes <query-timeout>300</query-timeout>

[ Any configured timeout for internal locks on the resource adapter objects in seconds The default is a 60 second timeout e.g. 5 minutes <use-try-lock>300</use-try-lock>

[ The allocation retry element indicates the number of times that allocating a connection should be tried before throwing an exception. The default is 0.

[ The allocation retry wait millis element indicates the time in milliseconds to wait between retrying to allocate a connection. The default is 5000 (5 seconds).

[ Passed to XAResource.setTransactionTimeout() Default is zero which does not invoke the setter. In seconds e.g. 5 minutes <xa-resource-timeout>300</xa-resource-timeout>

[ Whether to check for unclosed statements when a connection is returned to the pool and result sets are closed when a statement is closed/return to the prepared statement cache. valid values are: false - do not track statements and results true - track statements and result sets and warn when they are not closed nowarn - track statements but do no warn about them being unclosed (the default) e.g. <track-statements>nowarn</track-statements>

[ The number of prepared statements per connection in an LRU cache

[ Whether to share prepare statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement. The default is false. e.g. <share-prepared-statements/>

[ Specifies the security options used when creating a connection during recovery. Note: if this credential are not specified the security credential are used for recover too

[ Specifies the extension plugin used in spi (core.spi.xa) which can be implemented by various plugins to provide better feedback to the XA recovery system.

Name	Type	Default	Description
class-name	token

[ The fully qualifed name of the JDBC driver class Ex: <driver-class>org.hsqldb.jdbcDriver</driver-class>

[ The fully qualifed name of the javax.sql.XADataSource implementation class. Ex: <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>

[ The fully qualifed name of the javax.sql.DataSource implementation class.