en.help.ref-jdbcconnectionpoolnew2.html Maven / Gradle / Ivy
Show all versions of console-jdbc-plugin Show documentation
New JDBC Connection Pool (Step 2 of 2)
Use the New JDBC Connection Pool (Step 2 of 2) page to create a new JDBC connection pool.
The New JDBC Connection Pool (Step 2 of 2) page contains the following options.
- Datasource Classname
-
The vendor-specific class name that implements the DataSource
, ConnectionPoolDataSource
, or XADataSource
API. If you enabled the Introspect option and selected one of the datasource resource types, this field is 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.
- Driver Classname
-
The vendor-supplied JDBC driver class name. If you enabled the Introspect option and selected the java.sql.Driver
resource type, this field is 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.
- Ping
-
If this option is selected, the pool will be pinged automatically during pool creation or reconfiguration to identify and warn of any erroneous attribute values. This option is disabled by default.
- Description
-
A short description for the connection pool.
- Initial and Minimum Pool Size
-
The minimum number of connections in the pool. This value also determines the number of connections placed in the pool when the pool is first created or when GlassFish Server starts. The default value is 8.
- Maximum Pool Size
-
The maximum number of connections in the pool. The default value is 32.
- Pool Resize Quantity
-
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.
- Idle Timeout
-
The maximum amount of time, in seconds, that a connection can remain idle in the pool. After this time expires, the connection is removed from the pool. The default value is 300.
- Max Wait Time
-
The maximum amount of time, in milliseconds, that the application requesting a connection will wait before getting a connection timeout. The default value is 60,000.
- Non Transactional Connections
-
If this option is enabled, non-transactional connections are returned.
- Transaction Isolation
-
If a transaction isolation level is specified, connections in this pool operate at the specified level. Otherwise, the connections operate with default isolation levels provided by the JDBC driver. By default, this option is not specified.
- Isolation Level
-
If the Guaranteed checkbox is selected, all connections taken from the pool have the same isolation level. For example, if the isolation level for the connection is changed programmatically (with con.setTransactionIsolation
) when last used, then this mechanism changes the status back to the specified isolation level. This option is enabled by default.
This setting is only applicable if a transaction isolation level has been specified.
- Additional Properties
-
Additional properties for the JDBC connection pool. These properties might include database name (URL), user name, and password. The table normally contains properties used by the database vendor.
For a description of some of the available properties, see Properties Specific to JDBC Connection Pools.
If you do not specify a value for a property, it is removed from the table when you finish creating the connection pool. If you do not want to set a value for a property now, but you want the property to remain in the table so that the value can be set later, type a set of empty parentheses in the Value field:
()
Related Tasks
-
-
-
-
-
-
-
-
Related asadmin Commands
-
-
-
-
-
-
-
-
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices