The Connection Pools page opens.
The Edit Connection Pool page opens.
Choices include javax.sql.DataSource (local transactions only), javax.sql.XADataSource (global transactions), and java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements).
If you selected one of the datasource resource types, this field is usually filled in automatically with the class name associated with the resource type and database vendor you chose. If you selected the java.sql.Driver resource type, this field is disabled.
If you selected the java.sql.Driver resource type, this field is usually filled in automatically with the class name associated with the driver and database vendor you chose. If you selected one of the datasource resource types, this field is disabled.
This option is disabled by default.
This value also determines the number of connections placed in the pool when the pool is first created or when the GlassFish Server starts. The default value is 8.
The default value is 32.
When the pool scales up and scales down toward the maximum and minimum pool size respectively, it is resized in batches. This value determines the number of connections in the batch. Making this value too large delays connection creation and recycling; making it too small will be less efficient. The default value is 2.
After this time expires, the connection is removed from the pool. The default value is 300.
The default value is 60,000.
This option is disabled by default.
If not specified, the connections operate with default isolation levels provided by the JDBC driver. By default, this option is not specified.
For example, if the isolation level for the connection is changed programmatically (with con.setTransactionIsolation) when last used, this mechanism changes the status back to the specified isolation level.
This setting is only applicable if a transaction isolation level has been specified.
The Administration Console attempts to connect to the database. If an error message appears, check to see if the database server has been started.
Any existing live connections are destroyed, which means that the transactions associated with these connections are lost. The subcommand then recreates the initial connections for the pool, and restores the pool to its steady pool size.
Tip - To return to the default settings, click the Load Defaults button, then click Save.
See Also