GVDataSources - Revision history

Anonymous at 17:04, 14 February 2012

2012-02-14T17:04:10Z

Anonymous: /* xa-datasource */

2012-02-14T17:03:30Z

‎xa-datasource

Anonymous: /* no-tx-datasource */

2012-02-14T17:01:28Z

‎no-tx-datasource

Anonymous: /* local-tx-datasource */

2012-02-14T17:01:05Z

‎local-tx-datasource

Anonymous at 16:58, 14 February 2012

2012-02-14T16:58:57Z

Anonymous at 16:41, 14 February 2012

2012-02-14T16:41:15Z

Anonymous at 16:38, 14 February 2012

2012-02-14T16:38:51Z

Anonymous at 16:07, 14 February 2012

2012-02-14T16:07:15Z

Anonymous: /* local-tx-datasource */

2012-02-14T16:02:19Z

‎local-tx-datasource

Anonymous at 13:56, 14 February 2012

2012-02-14T13:56:53Z

@@ Line 209: / Line 209: @@
 * [[GVDataSources#xa-datasource-property|xa-datasource-property]]
 * isSameRM-override-value : The isSameRM-override-value element allows one to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns "true" or "false".
-* transaction-isolation :
+* transaction-isolation : Set java.sql.Connection transaction isolation level to use. The constants defined in the interface Connection are the possible transaction isolation levels and include:
 * user-name : Specifies the default username used when creating a new connection.
 * password : Specifies the default password used when creating a new connection.

@@ Line 205: / Line 205: @@
 * jndi-name : The JNDI name under which the DataSource wrapper will be bound. Note that this name is relative to the "java:/" prefix unless use-java-context is "false".
 * use-java-context : Setting this to "false" will bind the DataSource into global jndi.
-* track-connection-by-tx
+* track-connection-by-tx : An element to specify that all intermediate end(suspend) and start(resume) calls. Also, all work on one tx will go through one connection. A side effect of this (currently at least) is that a connection will only be usable by one tx until the tx commits.
 * [[GVDataSources#xa-datasource-class|xa-datasource-class]]
 * [[GVDataSources#xa-datasource-property|xa-datasource-property]]
-* isSameRM-override-value
+* isSameRM-override-value : The isSameRM-override-value element allows one to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns "true" or "false".
-* transaction-isolation
+* transaction-isolation :
 * user-name : Specifies the default username used when creating a new connection.
 * password : Specifies the default password used when creating a new connection.

@@ Line 266: / Line 266: @@
 * connection-url : The JDBC driver connection URL string.
 * driver-class : The fully qualified name of the JDBC driver class.
-* connection-property
+* connection-property : The connection-property element allows you to pass in arbitrary connection properties to the Driver.connect(url, props) method. Each connection-property specifies a string name/value pair with the property name coming from the name attribute and the value coming from the element content.
 * user-name : Specifies the default username used when creating a new connection.
 * password : Specifies the default password used when creating a new connection.

@@ Line 176: / Line 176: @@
 ** TRANSACTION_SERIALIZABLE
 ** TRANSACTION_NONE
-* connection-property
+* connection-property : The connection-property element allows you to pass in arbitrary connection properties to the Driver.connect(url, props) method. Each connection-property specifies a string name/value pair with the property name coming from the name attribute and the value coming from the element content.
 * user-name : Specifies the default username used when creating a new connection.
 * password : Specifies the default password used when creating a new connection.
@@ Line 182: / Line 182: @@
 * min-pool-size : 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.
 * max-pool-size : The max-pool-size element indicates the maximum number of connections for a pool. No more than MaxSize connections will be created in each sub-pool. This defaults to 20.
-* blocking-timeout-millis :  : 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).
+* blocking-timeout-millis : 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).
 * idle-timeout-minutes : 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.
 * [[GVDataSources#no-tx-separate-pools|no-tx-separate-pools]]

@@ Line 182: / Line 182: @@
 * min-pool-size : 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.
 * max-pool-size : The max-pool-size element indicates the maximum number of connections for a pool. No more than MaxSize connections will be created in each sub-pool. This defaults to 20.
-* blocking-timeout-millis
+* blocking-timeout-millis :  : 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).
-* idle-timeout-minutes
+* idle-timeout-minutes : 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.
 * [[GVDataSources#no-tx-separate-pools|no-tx-separate-pools]]
-* new-connection-sql
+* new-connection-sql : Specifies a SQL statement to execute whenever a connection is added to the connection pool.
-* check-valid-connection-sql
+* check-valid-connection-sql : Specifies an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.
-* valid-connection-checker-class-name
+* valid-connection-checker-class-name : An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides a SQLException
-* exception-sorter-class-name
+isValidConnection(Connection e) method to validate is a connection is valid. An exception means that the connection will be destroyed. This overrides the check-valid-connection-sql when present.
-* track-statements
+* exception-sorter-class-name : An org.jboss.resource.adapter.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.
-* prepared-statement-cache-size
+* track-statements : 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:
-* depends
+** false: do not track statements and results
-* type-mapping
+** true: track statements and result sets and warn when they are not closed
 ===xa-datasource===
@@ Line 211: / Line 215: @@
 * min-pool-size : 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.
 * max-pool-size : The max-pool-size element indicates the maximum number of connections for a pool. No more than MaxSize connections will be created in each sub-pool. This defaults to 20.
-* blocking-timeout-millis
+* blocking-timeout-millis : 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).
-* idle-timeout-minutes
+* idle-timeout-minutes : 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.
 * [[GVDataSources#no-tx-separate-pools|no-tx-separate-pools]]
-* new-connection-sql
+* new-connection-sql : Specifies a SQL statement to execute whenever a connection is added to the connection pool.
-* check-valid-connection-sql
+* check-valid-connection-sql : Specifies an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.
-* valid-connection-checker-class-name
+* valid-connection-checker-class-name : An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides a SQLException
-* exception-sorter-class-name
+isValidConnection(Connection e) method to validate is a connection is valid. An exception means that the connection will be destroyed. This overrides the check-valid-connection-sql when present.
-* track-statements
+* exception-sorter-class-name : An org.jboss.resource.adapter.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.
-* prepared-statement-cache-size
+* track-statements : 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:
-* depends
+** false: do not track statements and results
-* type-mapping
+** true: track statements and result sets and warn when they are not closed
 ====xa-datasource-class====
@@ Line 265: / Line 273: @@
 * max-pool-size : The max-pool-size element indicates the maximum number of connections for a pool. No more than MaxSize connections will be created in each sub-pool. This defaults to 20.
 * blocking-timeout-millis : 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).
-* idle-timeout-minutes
+* idle-timeout-minutes : 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.
-* new-connection-sql
+* new-connection-sql : Specifies a SQL statement to execute whenever a connection is added to the connection pool.
-* check-valid-connection-sql
+* check-valid-connection-sql : Specifies an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.
-* valid-connection-checker-class-name
+* valid-connection-checker-class-name : An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides a SQLException
-* exception-sorter-class-name
+isValidConnection(Connection e) method to validate is a connection is valid. An exception means that the connection will be destroyed. This overrides the check-valid-connection-sql when present.
-* track-statements
+* exception-sorter-class-name : An org.jboss.resource.adapter.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.
-* prepared-statement-cache-size
+* track-statements : 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:
-* depends
+** false: do not track statements and results
-* type-mapping
+** true: track statements and result sets and warn when they are not closed